Repository navigation
Open proxy / SSRF checks - #27
Merged
Merged
Conversation
emmanuelgautier
force-pushed
the
feat/ssrf-open-proxy
branch
from
November 9, 2026 23:53
4749fe1 to
d683ec3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #11.
Adds the
ssrfcategory (two aggressive-suite checks, run only with--aggressive) detecting whether the reverse proxy honors absolute-form request-targets and forwards to arbitrary hosts. Introduces a small raw-HTTP probe (ssrfprobe) since net/http only emits absolute-form targets in forward-proxy mode.ssrf.open_forward_proxy— sendsGET http://example.com/and confirms open-relay/SSRF behaviour only when the proxy returns that domain's content (which the backend never serves). Uses IANA's reserved example domain; the scanner never contacts it directly.ssrf.internal_target_access— reuses the forwarding primitive to probe the proxy's loopback, link-local cloud-metadata endpoints, and private RFC 1918 ranges. Differential and conservative: it learns how the proxy answers an unresolvable forward and flags only internal targets whose response is a success distinct from that baseline; skips entirely when the proxy serves its backend regardless of authority.Checklist coverage
docs/checks/ssrf.mdx)Includes registration, a category test (open-proxy vs reverse-proxy stand-ins), and a docs page.