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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-14234US | critical9.8 | Exploit | ||
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 djang… | ||||
references
External citations — patches, advisories, analysis.
- http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00025.htmlWEB
- https://docs.djangoproject.com/en/dev/releases/security/WEB
- https://github.com/advisories/GHSA-6r97-cj55-9hrqADVISORY
- https://groups.google.com/forum/#!topic/django-announce/jIoju2-KLDsWEB
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/STVX7X7IDWAH5SKE6MBMY3TEI6ZODBTK/WEB
- https://seclists.org/bugtraq/2019/Aug/15WEB
- https://security.gentoo.org/glsa/202004-17ADVISORY
- https://security.netapp.com/advisory/ntap-20190828-0002/ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan