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.8th percentile), scored .

Moderate probability of exploitation in the next 30 days — watch for active exploitation reports. 99th percentile — 98.8% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2019-14234: held from 0.477 to 0.477.

EPSS over last 30 days · oldest: 0.477 · newest: 0.477 · change: 0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2019-14234?
CVE-2019-14234 is a critical-severity vulnerability in Djangoproject Django, classified under SQL Injection. CVSS score: 9.8/10. Published 2019-08-09.
How severe is CVE-2019-14234?
Critical severity. CVSS v3 base score is 9.8 out of 10.
Is CVE-2019-14234 known to be exploited?
27 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.