Severity
- CVSS 3.x
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected versions
Repository
| Affected commits | Fixed by commit |
|---|---|
| GIT github.com/django/django ↗ | |
| c669cf279ae7b3e02a61db4fb077030a4db80e4f to before 974897759e9afc4cc56fb87e12319fa9697e93c9 | 974897759e9afc4cc56fb87e12319fa9697e93c9 |
| df591468251ed489a3e147d7c359f387f4effe66 to before ff9dcc0867eba90e9ab1b07a4b3eb79928717918 | ff9dcc0867eba90e9ab1b07a4b3eb79928717918 |
| 2a62cdcfec85938f40abb2e9e6a9ff497e02afe8 to before 8687fbe034ac5eec20e0948b98eb8a2f0b1431a1 | 8687fbe034ac5eec20e0948b98eb8a2f0b1431a1 |
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.
References
- Webgroups.google.com/forum/#%21topic/django-announce/jIoju2-KLDs ↗
- Weblists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/STVX7X7IDWAH5SKE6MBMY3TEI6ZODBTK/ ↗
- Advisorylists.opensuse.org/opensuse-security-announce/2019-08/msg00025.html ↗
- Advisorydocs.djangoproject.com/en/dev/releases/security/ ↗
- Advisoryseclists.org/bugtraq/2019/Aug/15 ↗
- Advisorysecurity.gentoo.org/glsa/202004-17 ↗
- Advisorysecurity.netapp.com/advisory/ntap-20190828-0002/ ↗
- Advisorywww.debian.org/security/2019/dsa-4498 ↗
- Advisorywww.djangoproject.com/weblog/2019/aug/01/security-releases/ ↗