CVE-2019-14234
- State
- Published
- Severity
- Not scored
- Published
- Aug 9, 2019
- Updated
- Aug 5, 2024
- Reserved
- Jul 22, 2019
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.
Scores
The record has no CVSS score.
Weaknesses
The record names no weakness.
Affected Products
| Product | Versions |
|---|---|
n/an/a |
|
References
- https://docs.djangoproject.com/en/dev/releases/security/
- https://groups.google.com/forum/#%21topic/django-announce/jIoju2-KLDs
- https://www.djangoproject.com/weblog/2019/aug/01/security-releases/
- 20190812 [SECURITY] [DSA 4498-1] python-django security updatemailing-list
- DSA-4498vendor-advisory
- openSUSE-SU-2019:1872vendor-advisory
- FEDORA-2019-647f74ce51vendor-advisory
- https://security.netapp.com/advisory/ntap-20190828-0002/
- GLSA-202004-17vendor-advisory
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.