Email Header Injection Protection Bypass
Open
Nobody has claimed this yet.
stdlib
topic-email
type-security
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 32606 |
|---|---|
| Nosy | @warsaw, @bitdancer, @csabella, @nitishch, @thedoctorsoup |
| Files |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2018-01-21.05:40:52.579>
labels = ['type-security', 'library']
title = 'Email Header Injection Protection Bypass'
updated_at = <Date 2018-09-29.16:09:33.569>
user = 'https://github.com/thedoctorsoup'
bugs.python.org fields:
activity = <Date 2018-09-29.16:09:33.569>
actor = 'cheryl.sabella'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-01-21.05:40:52.579>
creator = 'thedoctorsoup'
dependencies = []
files = ['47396']
hgrepos = []
issue_num = 32606
keywords = []
message_count = 4.0
messages = ['310367', '310904', '310911', '326682']
nosy_count = 5.0
nosy_names = ['barry', 'r.david.murray', 'cheryl.sabella', 'nitishch', 'thedoctorsoup']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'security'
url = 'https://bugs.python.org/issue32606'
versions = []
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked PythonEmailHeaderInjectionPOC.py proof of concept and the Python email library code it exercises. Reproduce the reported header-injection bypass, then identify the relevant regression-test location; done means the bypass is prevented and the regression test passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100