Skip to content

πŸ›‘οΈ Sentinel: [HIGH] Fix SSRF bypass via ISATAP tunneling addresses#74

Open
ManupaKDU wants to merge 1 commit into
mainfrom
sentinel-ssrf-isatap-2214781773707707780
Open

πŸ›‘οΈ Sentinel: [HIGH] Fix SSRF bypass via ISATAP tunneling addresses#74
ManupaKDU wants to merge 1 commit into
mainfrom
sentinel-ssrf-isatap-2214781773707707780

Conversation

@ManupaKDU
Copy link
Copy Markdown
Contributor

🚨 Severity: HIGH
πŸ’‘ Vulnerability: Server-Side Request Forgery (SSRF) bypass via ISATAP tunneling addresses. Python's ipaddress module evaluates ISATAP addresses as is_global = True without un-wrapping the embedded IPv4 address.
🎯 Impact: An attacker could bypass SSRF protections and scan or interact with restricted internal network addresses (e.g. 127.0.0.1 or 192.168.x.x) by encapsulating them in an ISATAP IPv6 address.
πŸ”§ Fix: Extracted the 32-bit ISATAP identifier to determine if the address is an ISATAP address (0x00005efe or 0x02005efe). If so, the embedded IPv4 address is manually extracted and validated against the SSRF blocklist.
βœ… Verification: Run python3 -m unittest test_testping1.py to run the updated test suite, which includes a test explicitly for this bypass vector.


PR created automatically by Jules for task 2214781773707707780 started by @ManupaKDU

Python's `ipaddress` module evaluates ISATAP addresses (e.g., `2000::5efe:127.0.0.1`) as `is_global = True` and does not automatically unwrap the embedded IPv4 address. This allows an attacker to bypass SSRF protections by encapsulating a restricted, private, or loopback IPv4 address inside an ISATAP IPv6 address.

This commit manually unwraps the IPv4 address from the ISATAP format by checking the 32-bit ISATAP identifier (`0x00005efe` or `0x02005efe`) and then validates the underlying IPv4 address against the SSRF rules. Tests have been added to verify that ISATAP bypasses are properly blocked.

Co-authored-by: ManupaKDU <95234271+ManupaKDU@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

πŸ‘‹ 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

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