Skip to content

πŸ›‘οΈ Sentinel: [HIGH] Fix SSRF bypass via SIIT (IPv4-translated) addresses#78

Merged
manupawickramasinghe merged 1 commit into
mainfrom
sentinel-ssrf-siit-bypass-12756634130325821454
May 17, 2026
Merged

πŸ›‘οΈ Sentinel: [HIGH] Fix SSRF bypass via SIIT (IPv4-translated) addresses#78
manupawickramasinghe merged 1 commit into
mainfrom
sentinel-ssrf-siit-bypass-12756634130325821454

Conversation

@ManupaKDU
Copy link
Copy Markdown
Contributor

πŸ›‘οΈ Sentinel: [HIGH] Fix SSRF bypass via SIIT (IPv4-translated) addresses

🚨 Severity: HIGH
πŸ’‘ Vulnerability: Python's ipaddress module evaluates SIIT (IPv4-translated) addresses (e.g., ::ffff:0:a.b.c.d) as is_global = True and does not expose them via the ipv4_mapped property. This allows an attacker to bypass standard SSRF filters by embedding loopback or private IPv4 addresses within the SIIT IPv6 structure, which the host OS network stack may then natively unwrap and route.
🎯 Impact: Attackers could bypass SSRF protections to scan or interact with internal/private IPs and the loopback interface on the host machine.
πŸ”§ Fix: Updated the manual IPv6 unpacking block in testping1.py to identify the SIIT prefix by checking if the high 96 bits equal 0xffff0000 (ip_int >> 32 == 0xffff0000). When matched, the embedded 32-bit IPv4 address is extracted and correctly subjected to the SSRF blocklist validation.
βœ… Verification: Added a test case test_is_reachable_ssrf_bypass_siit that ensures ::ffff:0:127.0.0.1 and ::ffff:0:192.168.1.1 are correctly rejected. Verified by running the test suite (python3 -m unittest test_testping1.py).


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

🚨 Severity: HIGH
πŸ’‘ Vulnerability: Python's `ipaddress` module evaluates SIIT (IPv4-translated) addresses (e.g., `::ffff:0:a.b.c.d`) as `is_global = True` and does not expose them via the `ipv4_mapped` property. This allows an attacker to bypass standard SSRF filters by embedding loopback or private IPv4 addresses within the SIIT IPv6 structure, which the host OS network stack may then natively unwrap and route.
🎯 Impact: Attackers could bypass SSRF protections to scan or interact with internal/private IPs and the loopback interface on the host machine.
πŸ”§ Fix: Updated the manual IPv6 unpacking block in `testping1.py` to identify the SIIT prefix by checking if the high 96 bits equal `0xffff0000` (`ip_int >> 32 == 0xffff0000`). When matched, the embedded 32-bit IPv4 address is extracted and correctly subjected to the SSRF blocklist validation.
βœ… Verification: Added a test case `test_is_reachable_ssrf_bypass_siit` that ensures `::ffff:0:127.0.0.1` and `::ffff:0:192.168.1.1` are correctly rejected. Verified by running the test suite (`python3 -m unittest test_testping1.py`).

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.

@manupawickramasinghe manupawickramasinghe merged commit 0003a7a into main May 17, 2026
1 check passed
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.

2 participants