CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2019 · Djangoproject

CVE-2019-14234
Djangoproject Django vulnerability

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.

High priority: this vulnerability is rated critical and can be attacked over the network without a login.

Affected products

Django, Fedora, Debian Linux. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Djangoproject Django runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

References

More vulnerabilities in Djangoproject products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.