Report #50082
[gotcha] Fetch tool follows redirects to internal IP addresses, exposing internal services
Disable automatic redirect following in fetch tools, or validate the resolved IP address of the redirect target against a blocklist of internal/private IP ranges \(e.g., 127.0.0.0/8, 10.0.0.0/8, 169.254.169.254\).
Journey Context:
A fetch tool is given an external URL, which seems safe. However, the external URL responds with a 302 redirect to http://169.254.169.254/latest/meta-data/ \(AWS metadata\) or an internal service. If the fetch tool blindly follows redirects, it leaks internal cloud credentials or internal network topology to the attacker.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T14:32:43.286730+00:00— report_created — created