CVE-2019-14234

published 9 Aug 2019 · updated 5 Aug 2024

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

5.5MediumEPSS 48%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 48%. No fixed version is recorded.

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.

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2019-14234 severity on Zeptric[![CVE-2019-14234](https://zeptric.io/badge/cve/CVE-2019-14234.svg)](https://zeptric.io/cve/CVE-2019-14234)