Skip to content

🛡️ Sentinel: [HIGH] Fix SSRF bypass via HTTP redirects#313

Open
seonghobae wants to merge 3 commits into
developfrom
sentinel/fix-ssrf-redirect-bypass-2657001790451947406
Open

🛡️ Sentinel: [HIGH] Fix SSRF bypass via HTTP redirects#313
seonghobae wants to merge 3 commits into
developfrom
sentinel/fix-ssrf-redirect-bypass-2657001790451947406

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

🚨 Severity: HIGH
💡 Vulnerability: Server-Side Request Forgery (SSRF) bypass through HTTP redirects. When a user provides an external URL that passes _is_safe_url validation, urllib.request.urlopen automatically follows redirects. If the external server redirects to an internal or restricted IP (e.g., http://127.0.0.1), the request succeeds, bypassing the initial safety checks.
🎯 Impact: Malicious actors could bypass SSRF guardrails and force the control plane or scanner to interact with internal infrastructure by configuring a webhook URL that redirects to internal IPs.
🔧 Fix: Replaced urllib.request.urlopen with a custom opener (build_opener) that includes a subclass of urllib.request.HTTPRedirectHandler which overrides redirect_request to return None. This explicitly blocks following any HTTP redirects.
Verification: Updated mocked tests to correctly intercept OpenerDirector.open and ensured full test suite passes.


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

Explicitly block HTTP redirects in URL fetchers to prevent SSRF bypasses.
When a user provides an external URL that passes `_is_safe_url` validation,
`urllib.request.urlopen` automatically follows redirects, which could point
to internal networks. Using a custom `HTTPRedirectHandler` prevents this.
@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.

Comment thread appguardrail_core/controlplane.py Fixed

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 1954f20337a5b62bc47b264355a1e01ec805ee8d.

  • Head SHA: 1954f20337a5b62bc47b264355a1e01ec805ee8d

  • Workflow run: 29423605574

  • Workflow attempt: 1

Coverage evidence

Coverage Decision

  • Result: FAIL
  • Test evidence: not proven passing
  • Docstring evidence: not proven passing when configured
  • Failure count: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (3 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (3 files)"]
  R1 --> V1["required checks"]
  Evidence --> S2["Test: test_controlplane.py"]
  S2 --> I2["regression suite"]
  I2 --> R2["Review risk: Test: test_controlplane.py"]
  R2 --> V2["targeted test run"]
Loading

@opencode-agent

opencode-agent Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: 5ff89015e6484efaa7f59da99c0948da81452e64
  • Workflow run: 29428565012
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 5ff89015e6484efaa7f59da99c0948da81452e64.

  • Head SHA: 5ff89015e6484efaa7f59da99c0948da81452e64

  • Workflow run: 29428565012

  • Workflow attempt: 1

Coverage evidence

Coverage Decision

  • Result: FAIL
  • Test evidence: not proven passing
  • Docstring evidence: not proven passing when configured
  • Failure count: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (3 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (3 files)"]
  R1 --> V1["required checks"]
  Evidence --> S2["Test: test_controlplane.py"]
  S2 --> I2["regression suite"]
  I2 --> R2["Review risk: Test: test_controlplane.py"]
  R2 --> V2["targeted test run"]
Loading

Explicitly block HTTP redirects in URL fetchers to prevent SSRF bypasses.
When a user provides an external URL that passes `_is_safe_url` validation,
`urllib.request.urlopen` automatically follows redirects, which could point
to internal networks. Using a custom `HTTPRedirectHandler` prevents this.

Also added nosemgrep annotation for python 3.7 compatibility false positive.
… compat

Explicitly block HTTP redirects in URL fetchers to prevent SSRF bypasses.
When a user provides an external URL that passes `_is_safe_url` validation,
`urllib.request.urlopen` automatically follows redirects, which could point
to internal networks. Using a custom `HTTPRedirectHandler` prevents this.

Also resolved a Python 3.7 compatibility issue flagged by Semgrep OSS by
adding a `try-except` fallback for `importlib.resources` to `importlib_resources`.

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 5ff89015e6484efaa7f59da99c0948da81452e64.

  • Head SHA: 5ff89015e6484efaa7f59da99c0948da81452e64

  • Workflow run: 29428565012

  • Workflow attempt: 1

Coverage evidence

Coverage Decision

  • Result: FAIL
  • Test evidence: not proven passing
  • Docstring evidence: not proven passing when configured
  • Failure count: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (3 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (3 files)"]
  R1 --> V1["required checks"]
  Evidence --> S2["Test: test_controlplane.py"]
  S2 --> I2["regression suite"]
  I2 --> R2["Review risk: Test: test_controlplane.py"]
  R2 --> V2["targeted test run"]
Loading

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