🛡️ Sentinel: [CRITICAL] Fix SSRF bypass via ISATAP tunneling#75
Conversation
🚨 Severity: CRITICAL 💡 Vulnerability: The Python `ipaddress` module evaluates ISATAP addresses (e.g., `2001:db8::5efe:127.0.0.1`) as globally routable (`is_global=True`) and does not natively expose or validate the encapsulated IPv4 payload. This allows an attacker to bypass standard SSRF filters by wrapping private or loopback IPv4 addresses in an ISATAP IPv6 structure. 🎯 Impact: Attackers could scan and interact with internal network resources (like 127.0.0.1 or 192.168.x.x) that are meant to be protected by the SSRF filter. 🔧 Fix: Manually identify ISATAP identifiers (`0000:5EFE` or `0200:5EFE`) within the 64-bit interface identifier of an IPv6 address using bitwise operations, extract the embedded 32-bit IPv4 address, and validate it against the existing SSRF blocklist rules. ✅ Verification: Verified by running the unit test suite (`python3 -m unittest test_testping1.py`), which includes a new test `test_is_reachable_ssrf_bypass_isatap` that confirms ISATAP payloads are properly blocked. Co-authored-by: ManupaKDU <95234271+ManupaKDU@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
2 participants
🚨 Severity: CRITICAL
💡 Vulnerability: The Python
ipaddressmodule evaluates ISATAP addresses (e.g.,2001:db8::5efe:127.0.0.1) as globally routable (is_global=True) and does not natively expose or validate the encapsulated IPv4 payload. This allows an attacker to bypass standard SSRF filters by wrapping private or loopback IPv4 addresses in an ISATAP IPv6 structure.🎯 Impact: Attackers could scan and interact with internal network resources (like 127.0.0.1 or 192.168.x.x) that are meant to be protected by the SSRF filter.
🔧 Fix: Manually identify ISATAP identifiers (
0000:5EFEor0200:5EFE) within the 64-bit interface identifier of an IPv6 address using bitwise operations, extract the embedded 32-bit IPv4 address, and validate it against the existing SSRF blocklist rules.✅ Verification: Verified by running the unit test suite (
python3 -m unittest test_testping1.py), which includes a new testtest_is_reachable_ssrf_bypass_isatapthat confirms ISATAP payloads are properly blocked.PR created automatically by Jules for task 13349946982675809614 started by @ManupaKDU