Skip to content

fix(syslog): Prevent Syslog TCP SSRF - #3816

Draft
ruslandoga wants to merge 7 commits into
Logflare:mainfrom
ruslandoga:rd/fix-syslog-tcp-ssrf
Draft

fix(syslog): Prevent Syslog TCP SSRF#3816
ruslandoga wants to merge 7 commits into
Logflare:mainfrom
ruslandoga:rd/fix-syslog-tcp-ssrf

Conversation

@ruslandoga

@ruslandoga ruslandoga commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Syslog TCP/TLS connections now resolve configured hosts at connection time with SSRF.safe_resolve_all/1, validate every address from one DNS result, and retry the pinned IPs sequentially, preventing DNS rebinding and internal port probing without losing OTP's hostname fallback behavior.

TLS still uses the original hostname for SNI and certificate verification, while explicitly configured single-tenant deployments retain private-network access.

safe_resolve/1 preserves its first-address contract for existing webhook/Finch consumers, and focused tests cover rejection, full-answer validation, address fallback, IP pinning, TLS identity, and the single-tenant exception.

Validated with 27 Syslog tests, 14 SSRF utility tests, targeted Credo, formatting, and diff checks.

@ruslandoga ruslandoga changed the title Prevent Syslog TCP SSRF fix(syslog): Prevent Syslog TCP SSRF Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant