First published: Tue Jul 30 2019(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/django | >=2.2.0<2.2.4 | 2.2.4 |
pip/django | >=2.1.0<2.1.11 | 2.1.11 |
pip/django | >=1.11.0<1.11.23 | 1.11.23 |
Djangoproject Django | >=1.11<1.11.23 | |
Djangoproject Django | >=2.1<2.1.11 | |
Djangoproject Django | >=2.2<2.2.4 | |
Fedoraproject Fedora | =30 | |
Debian Debian Linux | =9.0 | |
Debian Debian Linux | =10.0 | |
redhat/python-django | <0:1.11.27-1.el7 | 0:1.11.27-1.el7 |
redhat/python-django | <0:2.1.11-1.el8 | 0:2.1.11-1.el8 |
debian/python-django | 1:1.11.29-1~deb10u1 1:1.11.29-1+deb10u10 2:2.2.28-1~deb11u2 3:3.2.19-1+deb12u1 3:3.2.21-1 3:4.2.6-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID of this issue is CVE-2019-14234.
Django versions 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4 are affected by this vulnerability.
CVE-2019-14234 has a severity rating of 9.8, which is considered critical.
To fix this vulnerability, you should upgrade Django to version 1.11.23, 2.1.11, or 2.2.4.
You can find more information about CVE-2019-14234 in the following references: [Reference 1](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1735776), [Reference 2](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1735779), [Reference 3](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1735780).