-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
[3.6] bpo-39073: validate Address parts to disallow CRLF (GH-19007) #19224
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
Conversation
Disallow CR or LF in email.headerregistry.Address arguments to guard against header injection attacks. (cherry picked from commit 614f172) Co-authored-by: Ashwin Ramaswami <[email protected]>
@epicfaace and @bitdancer: Status check is done, and it's a success ✅ . |
1 similar comment
@epicfaace and @bitdancer: Status check is done, and it's a success ✅ . |
@epicfaace and @bitdancer: Status check is done, and it's a failure ❌ . |
@bitdancer Is this ready to merge? If so, I will merge to 3.6 for you. (Ignore the codecov check failure.) |
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.
@bitdancer approved the origin PR #19007 and requested backported to 3.6, 3.7 and 3.8:
#19007 (review)
So yeah, we must backport security fixes to stable branches. Since the CI pass, I merge the PR (by approving it).
@ned-deily: Would you mind to merge it? CI tests passed. 3.7 fix is already merged. |
@ned-deily: Please replace |
Disallow CR or LF in email.headerregistry.Address arguments to guard against header injection attacks.
(cherry picked from commit 614f172)
Co-authored-by: Ashwin Ramaswami [email protected]
https://bugs.python.org/issue39073