-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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.
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
gh-98433: Fix quadratic time idna decoding. #99092
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
365a6cb
gh-98433: Fix quadratic time idna decoding.
gpshead 4bf248b
drop the timing test, add an upfront limit.
gpshead db498cb
Expand the label limit comments.
gpshead be30a48
Also add a short "too long" test assert.
gpshead 038bbcd
Refactor into nicer code. Expand the NEWS entry.
gpshead cf3a20e
news wording tweak.
gpshead bd51456
more RFC links and explanation.
gpshead 5a3b037
assertRaisesRegex
gpshead File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
14 changes: 14 additions & 0 deletions
14
Misc/NEWS.d/next/Security/2022-11-04-09-29-36.gh-issue-98433.l76c5G.rst
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
The IDNA codec decoder used on DNS hostnames by :mod:`socket` or :mod:`asyncio` | ||
related name resolution functions no longer involves a quadratic algorithm. | ||
This prevents a potential CPU denial of service if an out-of-spec excessive | ||
length hostname involving bidirectional characters were decoded. Some protocols | ||
such as :mod:`urllib` http ``3xx`` redirects potentially allow for an attacker | ||
to supply such a name. | ||
|
||
Individual labels within an IDNA encoded DNS name will now raise an error early | ||
during IDNA decoding if they are longer than 1024 unicode characters given that | ||
each decoded DNS label must be 63 or fewer characters and the entire decoded | ||
DNS name is limited to 255. Only an application presenting a hostname or label | ||
consisting primarily of :rfc:`3454` section 3.1 "Nothing" characters to be | ||
removed would run into of this new limit. See also :rfc:`5894` section 6 and | ||
:rfc:`3491`. |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm okay with leaving this length limit out either entirely - or just out of the backports if release managers are uncomfortable with this in a bugfix.
I view it as protection from other as yet unknown future idna or punycode decoder logic bugs to avoid wasting cpu time. The only reference numbers related to my arbitrary input length limit choice are: A DNS hostname is 255 bytes at most. A label within a DNS name is 63 bytes at most.
The "Nothing" characters in question that are removed in
nameprep()
in https://github.com/python/cpython/blob/main/Lib/encodings/idna.py#L18 are non-ascii unicode oddities.Other IDNA decoding libraries in the wild like the well known ICU library do not limit the length at this level of API, instead leaving that to higher levels in the application: