Skip to content

fix: block shared/reserved IP ranges in SSRF guard#47

Open
threebeats wants to merge 1 commit into
profullstack:mainfrom
threebeats:fix/ssrf-guard-shared-ranges
Open

fix: block shared/reserved IP ranges in SSRF guard#47
threebeats wants to merge 1 commit into
profullstack:mainfrom
threebeats:fix/ssrf-guard-shared-ranges

Conversation

@threebeats

Copy link
Copy Markdown
Contributor

Fixes #43

Adds shared/reserved IP ranges to isBlockedIP:

  • 100.64.0.0/10 (Carrier-Grade NAT / RFC 6598)
  • 198.18.0.0/15 (Benchmarking / RFC 2544)
  • Documentation/example networks (RFC 5737)

Go's net.IsPrivate() covers RFC1918 but not these ranges.

Adds Carrier-Grade NAT (100.64.0.0/10), benchmarking (198.18.0.0/15),
and documentation/example (192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24)
ranges to the isBlockedIP check.

Go's net.IsPrivate() covers RFC1918 but not these shared/reserved ranges.

Fixes profullstack#43
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.

ASCII live SSRF guard allows shared and reserved IP ranges

2 participants