SQL Injection in Djangoproject Django
CVE-2019-14234
An 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. Due to an error in shallow key transformation, key and index lookups for django.contrib.postgres.fields.JSONField, and key lookups for django.contrib.postgres.fields.HStoreField, were subject to SQL injection. This could, for example, be exploited via crafted use of "OR 1=1" in a key or index name to return all records, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed to the QuerySet.filter() function.
Vulnerability class: SQL Injection
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.477, 98.9th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Djangoproject Django
- Debian Linux — versions 9.0, 10.0
- Fedoraproject Fedora — versions 30
Weakness classification (CWE)
Public exploits and proof-of-concept code
3 public repositories with exploit or proof-of-concept code for this CVE:
- malvika-thakur/CVE-2019-14234 (2 stars, last pushed 2023-09-15): POC-Django JSONField/HStoreField SQL Injection Vulnerability (CVE-2019-14234)
- giuliodamico/CVE-2019-14234 (last pushed 2026-06-05): CVE-2019-14234 — Django JSONField SQL Injection | Academic security project
- Rivaill/CVE_2019_14234
Also mentioned in 24 other repositories (ARPSyndicate/cvemon, bakery312/Vulhub-Reproduce, CLincat/vulcat, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- docs.djangoproject.com/en/dev/releases/security/ (Vendor Advisory)
- groups.google.com/forum/
- www.djangoproject.com/weblog/2019/aug/01/security-releases/ (Vendor Advisory)
- 20190812 [SECURITY] [DSA 4498-1] python-django security update (mailing-list, Mailing List, Third Party Advisory)
- DSA-4498 (vendor-advisory, Third Party Advisory)
- openSUSE-SU-2019:1872 (vendor-advisory, Mailing List, Third Party Advisory)
- FEDORA-2019-647f74ce51 (vendor-advisory)
- security.netapp.com/advisory/ntap-20190828-0002/
- GLSA-202004-17 (vendor-advisory)
This CVE has public exploit evidence. See the latest CVEs with public exploits.