Skip to content
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

[3.7] bpo-39073: validate Address parts to disallow CRLF (GH-19007) #19223

Merged
merged 1 commit into from
May 27, 2020

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Mar 30, 2020

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 aramaswamis@gmail.com

https://bugs.python.org/issue39073

 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 <aramaswamis@gmail.com>
@miss-islington
Copy link
Contributor Author

@epicfaace and @bitdancer: Status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
Contributor Author

@epicfaace and @bitdancer: Status check is done, and it's a success ✅ .

@ned-deily
Copy link
Member

@bitdancer Is this ready to merge?

Copy link
Member

@vstinner vstinner left a 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).

@miss-islington miss-islington merged commit a93bf82 into python:3.7 May 27, 2020
@miss-islington miss-islington deleted the backport-614f172-3.7 branch May 27, 2020 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-security A security issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants