Potential SQL injection via _connector keyword argument in QuerySet and Q objects
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.2.8, 5.1.14, 4.2.26
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 on Exploit-DB, 10 proofs of concept on GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
An issue was discovered in 5.1 before 5.1.14, 4.2 before 4.2.26, and 5.2 before 5.2.8. The methods `QuerySet.filter()`, `QuerySet.exclude()`, and `QuerySet.get()`, and the class `Q()`, are subject to SQL injection when using a suitably crafted dictionary, with dictionary expansion, as the `_connector` argument. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank cyberstan for reporting this issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Public exploit on Exploit-DB
EDB-52456
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- django
From 5.2 · fixed in 5.2.8; From 5.1 · fixed in 5.1.14; From 4.2 · fixed in 4.2.26
- djangoPyPI
From 5.2a1 · fixed in 5.2.8
- djangoPyPI
From 5.0a1 · fixed in 5.1.14
- djangoPyPI
fixed in 4.2.26
- djangoPyPI
From 4.2 · fixed in 4.2.26; From 5.1 · fixed in 5.1.14; From 5.2 · fixed in 5.2.8