mitre / mitre/secure-coding-case-studies
Proposal: Secure Coding Case Study for CVE-2024-36039 (SQL Injection in PyMySQL)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
We are proposing to write a case study on the SQL injection vulnerability in the PyMySQL library (CVE-2024-36039).
Description: PyMySQL through version 1.1.0 allows SQL injection if used with untrusted JSON input because dictionary keys are not escaped by the escape_dict function. An attacker can send specially crafted input to execute arbitrary SQL commands on the database, leading to unauthorized access or data manipulation.
Proposed vulnerability: CVE-2024-36039
Software: PyMySQL (Python MySQL client library)
Primary weakness: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVSS: 9.8 (Critical)
Group Members:
- Gondi Tarun Datta (G01547449)
- Goduguluri Varshitha (G01539592)
References:
Contributor guide
No contributing guide indexed for this repository
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 with the NVD entry and PyMySQL commit 521e40050cb386a499f68f483fefd144c493053c to verify the vulnerability details. Write the case study around CVE-2024-36039, including its SQL injection impact and the cited references; it is done when the repository has a complete, reviewable study consistent with its existing case-study format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, python
- Domain
- databases, documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100