Skip to content

πŸ›‘οΈ Sentinel: [HIGH] Fix Server-Side Request Forgery (SSRF) risk in plugin downloads - #243

Open
mttmcknn wants to merge 1 commit into
mainfrom
sentinel/ssrf-fix-6205668168245219430
Open

mttmcknn wants to merge 1 commit into
mainfrom
sentinel/ssrf-fix-6205668168245219430

Conversation

@mttmcknn

@mttmcknn mttmcknn commented Aug 8, 2026

Copy link
Copy Markdown
Owner
  • 🚨 Severity: HIGH
  • πŸ’‘ Vulnerability: http.Get was used directly for downloading plugins, allowing potential SSRF against cloud metadata endpoints.
  • 🎯 Impact: Attackers could potentially retrieve sensitive cloud instance metadata.
  • πŸ”§ Fix: Implemented newSafeHTTPClient with a custom DialContext hook that blocks connections to 169.254.169.254.
  • βœ… Verification: Tested by successfully running the repository's test suite (go test ./...) and ensuring build completion.

PR created automatically by Jules for task 6205668168245219430 started by @himattm

…wnloads

Replaced usage of `http.Get` for fetching user-provided plugin URLs with a custom `http.Client`. The new client (`newSafeHTTPClient`) includes an explicitly configured `net.Dialer` with a `Control` hook that intercepts socket connections *after* DNS resolution to evaluate the actual IP address being connected to. This blocks access to specific targeted cloud metadata endpoints (like 169.254.169.254), protecting against DNS rebinding and IP obfuscation SSRF attacks. Also introduces explicit timeouts for these external requests.

Co-authored-by: himattm <6266621+himattm@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