django
Affected
- introduced
1.11a1, fixed1.11.23(ecosystem)
Fixed versions
1.11.23
Fix
- Fixed version
1.11.23pip install --upgrade django==1.11.23
Advisory
Also known as: CVE-2019-14234, PYSEC-2019-13
SQL Injection in Django
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.
Critical Basis: The source's own band: CRITICAL
1.11a1, fixed 1.11.23 (ecosystem)1.11.23
1.11.23pip install --upgrade django==1.11.232.1a1, fixed 2.1.11 (ecosystem)2.1.11
2.1.11pip install --upgrade django==2.1.112.2a1, fixed 2.2.4 (ecosystem)2.2.4
2.2.4pip install --upgrade django==2.2.4Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0