CVE-2019-14234

Django: SQL injection possibility in key and index lookups for JSONField/HStoreField

Published Aug 9, 2019 CVSS 3.0 · 9.8 Critical EPSS 47.7% KEV · Not listed
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.

Analysis

No analysis available yet

Remediation

No remediation available yet

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DSA Debian DSA DSA-4498-1 python-django security update
Github GHSA Github GHSA GHSA-6r97-cj55-9hrq SQL Injection in Django
Ubuntu USN Ubuntu USN USN-4084-1 Django vulnerabilities
History

No history.

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Aug 5, 2024, 12:12 AM
Reserved
Jul 22, 2019, 12:00 AM
Status
Modified
Published
Aug 9, 2019, 1:15 PM
Modified
Jun 17, 2026, 2:18 AM
Severity
Moderate
Public date
Aug 1, 2019, 8:00 AM