This repository has been archived by the owner on Feb 22, 2024. It is now read-only.
Prevent open redirects when a malformed URL is passed to ?next= #318
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Example: "/login?next=http:///google.com" (note 3rd slash)
This is due to the way
urlparse.urlsplit
splits URLs. Specifically:Consequently, in the old
validate_redirect_url
function, which did this:This condition would not be met for malformed URLs and it would return
True
(valid URL).The included patch changes the code to return
False
if theurl_next
variable has a scheme andurl_next.netloc != url_base.netloc
(it's insufficient to simply check ifurl_next.netloc != url_base.netloc
because then relative redirects, such as?next=/index.html
fail). The fix is simply:This passes all the tests, and I can't think of any other nasty edge cases it might cause, but an alternative fix could be:
Credit to Muhammad Talha Khan for finding this.