CVE-2022-34265PYSEC-2022-213BIT-DJANGO-2022-34265GHSA-P64X-8RXX-WF6Q
An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.
- 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 3.2.14, 4.0.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 5 proofs of concept on GitHub
Summary
An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected.
Timeline
- CVE published
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- n/a n/a
Version range not reported
- djangoPyPI
From 3.2 · fixed in 3.2.14; From 4.0 · fixed in 4.0.6
- djangoPyPI
From 3.2a1 · fixed in 3.2.14
- djangoPyPI
From 4.0a1 · fixed in 4.0.6