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
Noroxi assessment
Priority: Plan (action score 42/100)
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Probability of exploitation in the next 30 days: 22.5% (FIRST EPSS); higher than 97.6% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: py-django (Alpine:v3.10) 1.11.29-r0; py3-django (Alpine:v3.11) 1.11.29-r0; python-django (Debian:12) 2:2.2.11-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Add it to your regular patch cycle. Upgrade to py-django (Alpine:v3.10) 1.11.29-r0; py3-django (Alpine:v3.11) 1.11.29-r0; python-django (Debian:12) 2:2.2.11-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
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.
- Published
- Mar 5, 2020
- Updated
- Jun 16, 2026
- EPSS
- 22.5% · 98th percentile
- CWE
- CWE-89
Report tools
Action score
42
Plan
Add it to your regular patch cycle.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 7 / 30 · 22.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| djangoproject | django | cpe:2.3:a:djangoproject:django |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| netapp | steelstore cloud integrated storage | cpe:2.3:a:netapp:steelstore_cloud_integrated_storage |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux19.10
- debian debian linux10.0
- debian debian linux9.0
- djangoproject django1.11 and later · before 1.11.29
- djangoproject django2.2 and later · before 2.2.11
- djangoproject django3.0 and later · before 3.0.4
- fedoraproject fedora31
- fedoraproject fedora32
- netapp steelstore cloud integrated storageall versions
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | py-django | before 1.11.29-r0 | 1.11.29-r0 |
| Alpine:v3.11 | py3-django | before 1.11.29-r0 | 1.11.29-r0 |
| Debian:12 | python-django | before 2:2.2.11-1 | 2:2.2.11-1 |
| Debian:9 | python-django | before 1:1.10.7-2+deb9u17 | 1:1.10.7-2+deb9u17 |
| PyPI | django | from 1.11 · before 1.11.29 | 1.11.29 |
| PyPI | django | from 2.2 · before 2.2.11 | 2.2.11 |
| PyPI | django | from 3.0 · before 3.0.4 | 3.0.4 |
| Red Hat:satellite_capsule:6.9::el7 | ansible-collection-redhat-satellite | before 0:2.0.1-1.el7sat | 0:2.0.1-1.el7sat |
| Red Hat:satellite_capsule:6.9::el7 | ansible-runner | before 0:1.4.6-1.el7ar | 0:1.4.6-1.el7ar |
| Red Hat:satellite_capsule:6.9::el7 | ansiblerole-foreman_scap_client | before 0:0.1.0-1.el7sat | 0:0.1.0-1.el7sat |
| Red Hat:satellite_capsule:6.9::el7 | ansiblerole-insights-client | before 0:1.7.1-1.el7sat | 0:1.7.1-1.el7sat |
| Red Hat:satellite_capsule:6.9::el7 | ansiblerole-satellite-receptor-installer | before 0:0.6.13-1.el7sat | 0:0.6.13-1.el7sat |
| Red Hat:satellite_capsule:6.9::el7 | crane-selinux | before 0:3.5.1-1.el7sat | 0:3.5.1-1.el7sat |
| Red Hat:satellite_capsule:6.9::el7 | createrepo_c | before 0:0.17.1-1.el7pc | 0:0.17.1-1.el7pc |
| Red Hat:satellite_capsule:6.9::el7 | createrepo_c-debuginfo | before 0:0.17.1-1.el7pc | 0:0.17.1-1.el7pc |
| Red Hat:satellite_capsule:6.9::el7 | createrepo_c-libs | before 0:0.17.1-1.el7pc | 0:0.17.1-1.el7pc |
| Red Hat:satellite_capsule:6.9::el7 | foreman | before 0:2.3.1.20-1.el7sat | 0:2.3.1.20-1.el7sat |
| Red Hat:satellite_capsule:6.9::el7 | foreman-bootloaders-redhat | before 0:202005201200-1.el7sat | 0:202005201200-1.el7sat |
| Red Hat:satellite_capsule:6.9::el7 | foreman-bootloaders-redhat-tftpboot | before 0:202005201200-1.el7sat | 0:202005201200-1.el7sat |
| Red Hat:satellite_capsule:6.9::el7 | foreman-debug | before 0:2.3.1.20-1.el7sat | 0:2.3.1.20-1.el7sat |
| Red Hat:satellite_capsule:6.9::el7 | foreman-discovery-image | before 1:3.7.4-2.el7sat | 1:3.7.4-2.el7sat |
| Red Hat:satellite_capsule:6.9::el7 | foreman-discovery-image-service | before 0:1.0.0-4.el7sat | 0:1.0.0-4.el7sat |
| Red Hat:satellite_capsule:6.9::el7 | foreman-discovery-image-service-tui | before 0:1.0.0-4.el7sat | 0:1.0.0-4.el7sat |
| Red Hat:satellite_capsule:6.9::el7 | foreman-installer | before 1:2.3.1.10-1.el7sat | 1:2.3.1.10-1.el7sat |
+96
Same product
djangoproject: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-34265An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.61This week
- CVE-2020-7471Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter 59Plan
- CVE-2019-19844Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.55Plan
- CVE-2019-14234An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4.53Plan
- CVE-2021-35042Django 3.1.x before 3.1.13 and 3.2.x before 3.2.5 allows QuerySet.order_by SQL injection if order_by is untrusted input from a client of a w52Plan
- CVE-2023-24580An issue was discovered in the Multipart Request Parser in Django 3.2 before 3.2.18, 4.0 before 4.0.10, and 4.1 before 4.1.7.49Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:py-django | 1.11.29-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:py3-django | 1.11.29-r0 · Alpine:v3.11 | Package registry (OSV) |
| debian:python-django | 2:2.2.11-1 · Debian:12 | Package registry (OSV) |
| PyPI:django | 1.11.29 | Package registry (OSV) |
| PyPI:django | 2.2.11 | Package registry (OSV) |
| PyPI:django | 3.0.4 | Package registry (OSV) |
| red hat:ansible-collection-redhat-satellite | 0:2.0.1-1.el7sat · Red Hat:satellite_capsule:6.9::el7 | Package registry (OSV) |
| red hat:ansible-runner | 0:1.4.6-1.el7ar · Red Hat:satellite_capsule:6.9::el7 | Package registry (OSV) |
| red hat:ansiblerole-foreman_scap_client | 0:0.1.0-1.el7sat · Red Hat:satellite_capsule:6.9::el7 | Package registry (OSV) |
| red hat:ansiblerole-insights-client | 0:1.7.1-1.el7sat · Red Hat:satellite_capsule:6.9::el7 | Package registry (OSV) |
| red hat:ansiblerole-satellite-receptor-installer | 0:0.6.13-1.el7sat · Red Hat:satellite_capsule:6.9::el7 | Package registry (OSV) |
| red hat:crane-selinux | 0:3.5.1-1.el7sat · Red Hat:satellite_capsule:6.9::el7 | Package registry (OSV) |
| red hat:createrepo_c | 0:0.17.1-1.el7pc · Red Hat:satellite_capsule:6.9::el7 | Package registry (OSV) |
| red hat:createrepo_c-debuginfo | 0:0.17.1-1.el7pc · Red Hat:satellite_capsule:6.9::el7 | Package registry (OSV) |
| red hat:createrepo_c-libs | 0:0.17.1-1.el7pc · Red Hat:satellite_capsule:6.9::el7 | Package registry (OSV) |
| red hat:foreman | 0:2.3.1.20-1.el7sat · Red Hat:satellite_capsule:6.9::el7 | Package registry (OSV) |
| red hat:foreman-bootloaders-redhat | 0:202005201200-1.el7sat · Red Hat:satellite_capsule:6.9::el7 | Package registry (OSV) |
| red hat:foreman-bootloaders-redhat-tftpboot | 0:202005201200-1.el7sat · Red Hat:satellite_capsule:6.9::el7 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Nuclei detection template ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Nuclei detection template | Nuclei template CVE-2020-9402 | — |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-301 · May 4, 2020(Django Güvenlik Güncellemesi Yayınladı)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.
The bug in code
The whole CWE-89 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const owner = req.query.owner;const rows = await db.query( "SELECT * FROM files WHERE owner = '" + owner + "'");Fixed
const owner = req.query.owner;const rows = await db.query( "SELECT * FROM files WHERE owner = $1", [owner]);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Expanding Control over the Operating System from the DatabaseCAPEC-470Very High
- SQL InjectionCAPEC-66likelihood: High · High
- Blind SQL InjectionCAPEC-7likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- groups.google.com/forum/#%21topic/django-announce/fLUh_pOaKrY
- lists.debian.org/debian-lts-announce/2022/05/msg00035.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4A2AP4T7RKPBCLTI2NNQG3T6MINDUUMZ/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UZMN2NKAGTFE3YKMNM2JVJG7R2W7LLHY/
- security.gentoo.org/glsa/202004-17
- security.netapp.com/advisory/ntap-20200327-0004/
- usn.ubuntu.com/4296-1/
- www.debian.org/security/2020/dsa-4705
- www.djangoproject.com/weblog/2020/mar/04/security-releases/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.