Repository navigation
gh-161104: Check the http.client tunnel host after IDNA encoding - #161105
Merged
Merged
Conversation
IDNA normalization maps U+00A0 and similar characters to an ASCII space, so check the encoded host that is put into the CONNECT request line.
gpshead
marked this pull request as ready for review
November 1, 2026 18:13
gpshead
enabled auto-merge (squash)
November 1, 2026 18:14
Member
Author
|
I marked this for full backporting security style as it might be a way that #146211 could be bypassed. FYI @sethmlarson ie: if so we should move the news entry to Security. |
gpshead
disabled auto-merge
November 1, 2026 18:22
sethmlarson
approved these changes
Nov 12, 2026
|
Thanks @gpshead for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14, 3.15. |
|
GH-161880 is a backport of this pull request to the 3.15 branch. |
|
GH-161881 is a backport of this pull request to the 3.14 branch. |
gpshead
added a commit
that referenced
this pull request
Nov 12, 2026
…ng (GH-161105) (#161880) gh-161104: Check the http.client tunnel host after IDNA encoding (GH-161105) IDNA normalization maps U+00A0 and similar characters to an ASCII space, so check the encoded host that is put into the CONNECT request line. ANT-2026-PIZPMECM (cherry picked from commit 7ac989f) Co-authored-by: Gregory P. Smith <68491+gpshead@users.noreply.github.com>
gpshead
added a commit
that referenced
this pull request
Nov 14, 2026
…ng (GH-161105) (#161881) gh-161104: Check the http.client tunnel host after IDNA encoding (GH-161105) IDNA normalization maps U+00A0 and similar characters to an ASCII space, so check the encoded host that is put into the CONNECT request line. ANT-2026-PIZPMECM (cherry picked from commit 7ac989f) Co-authored-by: Gregory P. Smith <68491+gpshead@users.noreply.github.com>
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Encode the tunnel host with IDNA first and run the existing disallowed-character check on the bytes that go into the
CONNECTrequest line. IDNA passes ASCII through unchanged, so every host refused today is still refused with the same message; the only newly refused hosts are those whose encoding contains a space.The
Hostheader built inputrequest()has the same encode-after-check order, but a host like that can't be resolved for a direct connection, so it is left alone here.Fixes #161104
ANT-2026-PIZPMECM
HTTPConnection.set_tunnel()host check runs before IDNA maps U+00A0 to a space #161104