Improper Input Validation in urlparse
Open
Nobody has claimed this yet.
3.9 (EOL)
stdlib
type-security
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 46870 |
|---|---|
| Nosy | @orsenthil, @P0cas, @lafolle |
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 2022-02-27.01:12:03.440>
labels = ['type-security', '3.9']
title = 'Improper Input Validation in urlparse'
updated_at = <Date 2022-03-02.13:38:56.216>
user = 'https://github.com/P0cas'
bugs.python.org fields:
activity = <Date 2022-03-02.13:38:56.216>
actor = 'P0cas'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2022-02-27.01:12:03.440>
creator = 'P0cas'
dependencies = []
files = []
hgrepos = []
issue_num = 46870
keywords = []
message_count = 4.0
messages = ['414132', '414133', '414171', '414345']
nosy_count = 3.0
nosy_names = ['orsenthil', 'P0cas', 'karanchaudhary']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'security'
url = 'https://bugs.python.org/issue46870'
versions = ['Python 3.9']
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 locating urlparse and its existing tests, then recover the missing reproduction and expected behavior from BPO issue 46870 and its migrated messages. The issue is complete when the improper input is consistently handled as specified and regression coverage verifies the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100