CVE-2019-14234

Description

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.

How to fix CVE-2019-14234

To remediate CVE-2019-14234, upgrade the affected package to a fixed version below.

• —upgrade to 1.11.23-r0 or later
• —upgrade to 1.11.23-r0 or later
• —upgrade to 2:2.2.4-1 or later
• —upgrade to 1.11.23 or later
• —upgrade to 2.1.11 or later

Is CVE-2019-14234 being exploited?

Moderate — EPSS is 29.7%. Track this CVE but it's not at the top of the prioritisation list.

Affected packages (5)

• from 0, < 1.11.23-r0
• from 0, < 1.11.23-r0
• from 0, < 2:2.2.4-1
• >= 1.11a1, < 1.11.23
• >= 2.1, < 2.1.11, >= 1.11, < 1.11.23, >= 2.2, < 2.2.4

CVSS scores

References (22)

• ADVISORYgithub.com/advisories/GHSA-6r97-cj55-9hrq
• ADVISORYnvd.nist.gov/vuln/detail/CVE-2019-14234
• ADVISORYsecurity.alpinelinux.org/vuln/CVE-2019-14234
• ADVISORYsecurity.netapp.com/advisory/ntap-20190828-0002/
• ADVISORY