Skip to content

🛡️ Sentinel: [HIGH] Fix SSRF vulnerability in path routes - #73

Merged
frkr merged 2 commits into
mainfrom
sentinel-ssrf-paths-487501659224268239
Jun 11, 2026
Merged

🛡️ Sentinel: [HIGH] Fix SSRF vulnerability in path routes#73
frkr merged 2 commits into
mainfrom
sentinel-ssrf-paths-487501659224268239

Conversation

@frkr

@frkr frkr commented May 28, 2026

Copy link
Copy Markdown
Owner

🚨 Severity: HIGH
💡 Vulnerability: Server-Side Request Forgery (SSRF) via invalid URL protocols. The application used new URL(destiny) and new URL(callback) to validate inputs, which allows protocols like file:// and ftp://. Since these inputs are later used in server-side fetch calls, an attacker could potentially force the server to read local files or connect to internal services.
🎯 Impact: Potential unauthorized access to internal networks or local file reading on the server.
🔧 Fix: Explicitly validate url.protocol and reject anything that isn't http: or https:. Added unit tests for these cases.
Verification: Run pnpm run test test/front/.server/panel/paths.spec.ts and see that tests pass checking for SSRF protection.


PR created automatically by Jules for task 487501659224268239 started by @frkr

- Add strict validation for `destiny` and `callback` URLs to ensure they only use `http:` or `https:` protocols.
- Prevents Server-Side Request Forgery (SSRF) attacks where an attacker could provide `ftp://` or `file://` URLs.
- Update relevant unit tests to assert invalid protocols throw an error.
- Log discovery in .jules/sentinel.md.

Co-authored-by: frkr <185359+frkr@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.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented May 28, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
❌ Deployment failed
View logs
cfgateway 3922473 Jun 11 2026, 06:11 PM

@frkr frkr closed this May 30, 2026
@frkr
frkr deleted the sentinel-ssrf-paths-487501659224268239 branch May 30, 2026 20:58
@frkr
frkr restored the sentinel-ssrf-paths-487501659224268239 branch June 11, 2026 18:10
@frkr frkr reopened this Jun 11, 2026
Signed-off-by: Davi <davimesquita@gmail.com>
@frkr
frkr merged commit 116d88a into main Jun 11, 2026
2 checks passed
@frkr
frkr deleted the sentinel-ssrf-paths-487501659224268239 branch June 11, 2026 18:10
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