Skip to content

gh-96035: Make urllib.parse.urlparse reject non-numeric ports #98273

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 14 commits into from
Oct 20, 2022
Merged

gh-96035: Make urllib.parse.urlparse reject non-numeric ports #98273

merged 14 commits into from
Oct 20, 2022

Conversation

kenballus
Copy link
Contributor

@kenballus kenballus commented Oct 15, 2022 •
edited by bedevere-bot
Loading

urllib.parse.urlparse uses int to parse port numbers, which means they can contain signs, underscores, and whitespace. This patch adds a check to ensure that only numeric port numbers parse without error.

@kenballus kenballus changed the title pythongh-96035: Make urllib.parse.urlparse reject non-numeric ports gh-96035: Make urllib.parse.urlparse reject non-numeric ports Oct 15, 2022
JelleZijlstra
JelleZijlstra reviewed Oct 15, 2022
View reviewed changes
JelleZijlstra
JelleZijlstra requested changes Oct 15, 2022
View reviewed changes
Copy link
Member

@JelleZijlstra JelleZijlstra left a comment

Choose a reason for hiding this comment

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

We'll also need new tests for this behavior.

@bedevere-bot
Copy link

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@kenballus
Copy link
Contributor Author

@JelleZijlstra

I think it makes way more sense to move port validation entirely to parse time, a la #25774, so it might not make sense to implement these fixes until that happens. What's the protocol for PRs that depend on other PRs? Should I make a PR into @gpshead's fork, or would you rather I submit this in isolation and have other adjust for it?

Thanks!

@JelleZijlstra
Copy link
Member

I'd also want to hear @gpshead's opinion, and I haven't looked at #25774 in enough detail to understand the problem it's trying to solve. However, the other PR has been open for a long time and looks like a more invasive change, so we may want to apply it only on main, while this PR is a more self-contained bugfix that we'll be able to backport to 3.10 and 3.11.

gpshead
gpshead requested changes Oct 17, 2022
View reviewed changes
Copy link
Member

@gpshead gpshead left a comment

Choose a reason for hiding this comment

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

Please add a unittest that would trigger this error code path.

@kenballus kenballus requested review from JelleZijlstra and gpshead and removed request for JelleZijlstra October 20, 2022 02:25
@kenballus kenballus requested review from JelleZijlstra and removed request for gpshead October 20, 2022 02:31
JelleZijlstra
JelleZijlstra reviewed Oct 20, 2022
View reviewed changes
Copy link
Member

@JelleZijlstra JelleZijlstra left a comment

Choose a reason for hiding this comment

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

There's another case to consider: Unicode digits! For example, your patch still allows a port of ६, which is the Devanagari character for 6. Your quote from the RFC on the issue says only ASCII digits are allowed.

@kenballus
Copy link
Contributor Author

There's another case to consider: Unicode digits! For example, your patch still allows a port of ६, which is the Devanagari character for 6. Your quote from the RFC on the issue says only ASCII digits are allowed.

Great catch! I had no idea that things like "६".isdigit() == True! I'll fix that right away.

JelleZijlstra
JelleZijlstra reviewed Oct 20, 2022
View reviewed changes
@JelleZijlstra JelleZijlstra merged commit 6f15ca8 into python:main Oct 20, 2022
@JelleZijlstra JelleZijlstra added needs backport to 3.10 only security fixes needs backport to 3.11 only security fixes labels Oct 20, 2022
@miss-islington
Copy link
Contributor

Thanks @kenballus for the PR, and @JelleZijlstra for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10.
🐍🍒⛏🤖

@miss-islington
Copy link
Contributor

Thanks @kenballus for the PR, and @JelleZijlstra for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Oct 20, 2022
@kenballus @miss-islington
pythongh-96035: Make urllib.parse.urlparse reject non-numeric ports (p…
1bae88c 
…ythonGH-98273)

Co-authored-by: Jelle Zijlstra <[email protected]>
(cherry picked from commit 6f15ca8)

Co-authored-by: Ben Kallus <[email protected]>
@bedevere-bot
Copy link

GH-98498 is a backport of this pull request to the 3.10 branch.

@bedevere-bot bedevere-bot removed the needs backport to 3.10 only security fixes label Oct 20, 2022
@bedevere-bot
Copy link

GH-98499 is a backport of this pull request to the 3.11 branch.

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Oct 20, 2022
@kenballus @miss-islington
pythongh-96035: Make urllib.parse.urlparse reject non-numeric ports (p…
c0f3576 
…ythonGH-98273)

Co-authored-by: Jelle Zijlstra <[email protected]>
(cherry picked from commit 6f15ca8)

Co-authored-by: Ben Kallus <[email protected]>
@bedevere-bot bedevere-bot removed the needs backport to 3.11 only security fixes label Oct 20, 2022
miss-islington added a commit that referenced this pull request Oct 20, 2022
@miss-islington @kenballus
gh-96035: Make urllib.parse.urlparse reject non-numeric ports (GH-98273)
1520f4e 
Co-authored-by: Jelle Zijlstra <[email protected]>
(cherry picked from commit 6f15ca8)

Co-authored-by: Ben Kallus <[email protected]>
miss-islington added a commit that referenced this pull request Oct 20, 2022
@miss-islington @kenballus
gh-96035: Make urllib.parse.urlparse reject non-numeric ports (GH-98273)
0db4c59 
Co-authored-by: Jelle Zijlstra <[email protected]>
(cherry picked from commit 6f15ca8)

Co-authored-by: Ben Kallus <[email protected]>
@kenballus kenballus mentioned this pull request Nov 12, 2022
Merged
haq204 pushed a commit to emissary-ingress/emissary that referenced this pull request Dec 20, 2022
python: update unit tests
25f6178 
python 3.10.9 introduced python/cpython#98273 which fixes a bug in `urllib.parse.urlparse()` where certain port numbers containing whitespaces or other non-ASCII digits to be erroneously allowed. But it also changed the error message that was expected in one of our unit tests. So update our unit tests to expect the new error message.

NOTE: the new error message is slightly confusing for certain port numbers (e.g -1) due to its use of `str.isdigit()` to flag whether the port could be cast as an int.

Signed-off-by: Hamzah Qudsi <[email protected]>
haq204 pushed a commit to emissary-ingress/emissary that referenced this pull request Dec 20, 2022
python: update unit tests
4bf2433 
python 3.10.9 introduced python/cpython#98273 which fixes a bug in `urllib.parse.urlparse()` where certain port numbers containing whitespaces or other non-ASCII digits to be erroneously allowed. But it also changed the error message that was expected in one of our unit tests. So update our unit tests to expect the new error message.

NOTE: the new error message is slightly confusing for certain port numbers (e.g -1) due to its use of `str.isdigit()` to flag whether the port could be cast as an int.

Signed-off-by: Hamzah Qudsi <[email protected]>
@haq204 haq204 mentioned this pull request Dec 27, 2022
Merged
6 tasks
haq204 pushed a commit to emissary-ingress/emissary that referenced this pull request Dec 27, 2022
python: update unit tests
ee90961 
python 3.10.9 introduced python/cpython#98273 which fixes a bug in `urllib.parse.urlparse()` where certain port numbers containing whitespaces or other non-ASCII digits to be erroneously allowed. But it also changed the error message that was expected in one of our unit tests. So update our unit tests to expect the new error message.

NOTE: the new error message is slightly confusing for certain port numbers (e.g -1) due to its use of `str.isdigit()` to flag whether the port could be cast as an int.

Signed-off-by: Hamzah Qudsi <[email protected]>
haq204 pushed a commit to emissary-ingress/emissary that referenced this pull request Dec 28, 2022
@haq204
python: update unit tests
5256926 
python 3.10.9 introduced python/cpython#98273 which fixes a bug in `urllib.parse.urlparse()` where certain port numbers containing whitespaces or other non-ASCII digits to be erroneously allowed. But it also changed the error message that was expected in one of our unit tests. So update our unit tests to expect the new error message.

NOTE: the new error message is slightly confusing for certain port numbers (e.g -1) due to its use of `str.isdigit()` to flag whether the port could be cast as an int.

Signed-off-by: Hamzah Qudsi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@gpshead gpshead gpshead approved these changes

@JelleZijlstra JelleZijlstra JelleZijlstra approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@kenballus @bedevere-bot @JelleZijlstra @miss-islington @gpshead