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.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2019-14234 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.11.23, 2.1.11, 2.2.4); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2019-14234? CVE-2019-14234 is a critical-severity SQL injection vulnerability in Django (pip), affecting versions >= 1.11a1, < 1.11.23. It is fixed in 1.11.23, 2.1.11, 2.2.4. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2019-14234? CVE-2019-14234 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of Django are affected by CVE-2019-14234? Django (pip) versions >= 1.11a1, < 1.11.23 is affected.
4. Is there a fix for CVE-2019-14234? Yes. CVE-2019-14234 is fixed in 1.11.23, 2.1.11, 2.2.4. Upgrade to this version or later.
5. Is CVE-2019-14234 exploitable, and should I be worried? Whether CVE-2019-14234 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2019-14234 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2019-14234?
   • Upgrade Django to 1.11.23 or later
   • Upgrade Django to 2.1.11 or later
   • Upgrade Django to 2.2.4 or later