CVE-2020-9402PYSEC-2020-36BIT-DJANGO-2020-9402GHSA-3GH2-XW74-JMCWPYSEC-2020-345
Django 1.11 before 1.11.29, 2.2 before 2.2.11, and 3.0 before 3.0.4 allows SQL Injection if untrusted data is used as a tolerance parameter
- 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 1.11.29, 2.2.11, 3.0.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Django 1.11 before 1.11.29, 2.2 before 2.2.11, and 3.0 before 3.0.4 allows SQL Injection if untrusted data is used as a tolerance parameter in GIS functions and aggregates on Oracle. By passing a suitably crafted tolerance to GIS functions and aggregates on Oracle, it was possible to break escaping and inject malicious SQL.
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 1.11 · fixed in 1.11.29; From 2.2 · fixed in 2.2.11; From 3.0 · fixed in 3.0.4
- djangoPyPI
From 1.11 · fixed in 1.11.29
- djangoPyPI
From 2.2 · fixed in 2.2.11
- djangoPyPI
From 3.0 · fixed in 3.0.4