Skip to content

fix(security): [HIGH] resolve Open Redirect vulnerability in URL validation#93

Open
Tugamer89 wants to merge 1 commit into
mainfrom
fix/open-redirect-security-1480532950398926126
Open

fix(security): [HIGH] resolve Open Redirect vulnerability in URL validation#93
Tugamer89 wants to merge 1 commit into
mainfrom
fix/open-redirect-security-1480532950398926126

Conversation

@Tugamer89

Copy link
Copy Markdown
Owner

Severity: HIGH

Vulnerability:
The get_safe_redirect_url function, designed to prevent Open Redirects, was vulnerable to a bypass. Python's urllib.parse.urlparse treats URLs like http:evil.com or http:///evil.com as having a valid scheme (http) but an empty netloc. The original code only checked that parsed.netloc != request_host, meaning these malformed URLs would bypass the netloc check completely.

Impact:
An attacker could craft a malicious URL with this format, bypass the get_safe_redirect_url check, and redirect unsuspecting users to a malicious external site.

Fix:
Added an explicit check in core/security.py's get_safe_redirect_url function to return / if parsed.scheme is present but parsed.netloc is not. This explicitly blocks these types of malformed URLs.

Verification:

  • Tested manually with malformed URLs like http:evil.com and http:///evil.com, which correctly return /.
  • Verified valid local paths like /dashboard and valid same-host URLs like http://localhost/dashboard are allowed.
  • Ran the automated test suite and linter with no failures or regressions.

PR created automatically by Jules for task 1480532950398926126 started by @Tugamer89

Modified get_safe_redirect_url to check if scheme is present but netloc
is empty, fixing an open redirect bypass via malformed URLs like 'http:evil.com'
or 'http:///evil.com'.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@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.

@sonarqubecloud

Copy link
Copy Markdown

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