Skip to content

πŸ›‘οΈ Sentinel: [HIGH] Fix SSRF via HTTP Redirects - #415

Open
seonghobae wants to merge 2 commits into
developfrom
sentinel-fix-ssrf-redirects-16119752968268062907
Open

πŸ›‘οΈ Sentinel: [HIGH] Fix SSRF via HTTP Redirects#415
seonghobae wants to merge 2 commits into
developfrom
sentinel-fix-ssrf-redirects-16119752968268062907

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

🚨 Severity: HIGH
πŸ’‘ Vulnerability: Server-Side Request Forgery (SSRF) bypass due to urllib.request.urlopen blindly following HTTP redirects. An attacker could provide an allowed external URL (like https://github.com/) that subsequently returns a 301 or 302 redirect to an internal, private, or loopback IP (like http://127.0.0.1/).
🎯 Impact: An attacker could bypass the _is_safe_url checks on the initial request and successfully make requests to internal services, potentially interacting with sensitive infrastructure.
πŸ”§ Fix:

  • Created a custom SafeRedirectHandler (inheriting from urllib.request.HTTPRedirectHandler) in both appguardrail_core/controlplane.py and scanner/cli/appguardrail.py.
  • Overrode the redirect_request method to explicitly call _is_safe_url on any new redirect URL, raising urllib.error.URLError if the URL resolves to an unsafe address.
  • Changed the invocations of urllib.request.urlopen to use urllib.request.build_opener(SafeRedirectHandler()).open().
    βœ… Verification:
  • Modified unit tests in test_controlplane.py to mock build_opener instead of urlopen.
  • Added a specific regression test test_safe_redirect_blocks_unsafe_url in tests/test_ssrf_protection.py to verify that URLError is raised when the redirect attempts to resolve to loopback (127.0.0.1) or link-local (169.254.169.254). All tests pass perfectly.

PR created automatically by Jules for task 16119752968268062907 started by @seonghobae

@google-labs-jules

Copy link
Copy Markdown

πŸ‘‹ 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.

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 13 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
βš™οΈ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c4cea52c-c364-4cb5-9d33-d4f53069db9b

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 906c362 and 75a5a93.

πŸ“’ Files selected for processing (5)
  • .jules/sentinel.md
  • appguardrail_core/controlplane.py
  • scanner/cli/appguardrail.py
  • tests/test_controlplane.py
  • tests/test_ssrf_protection.py

Comment @coderabbitai help to get the list of available commands.

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