Advisory

GHSA-6r97-cj55-9hrq

Also known as: CVE-2019-14234, PYSEC-2019-13

Summary

SQL Injection in Django

Details

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.

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2019-08-16 14:00 UTC
Modified
2025-02-21 05:50 UTC

Affected packages and fixes

django

PyPI · All systems

Affected

  • introduced 1.11a1, fixed 1.11.23 (ecosystem)

Fixed versions

1.11.23

Fix

  • Fixed version 1.11.23
    pip install --upgrade django==1.11.23

django

PyPI · All systems

Affected

  • introduced 2.1a1, fixed 2.1.11 (ecosystem)

Fixed versions

2.1.11

Fix

  • Fixed version 2.1.11
    pip install --upgrade django==2.1.11

django

PyPI · All systems

Affected

  • introduced 2.2a1, fixed 2.2.4 (ecosystem)

Fixed versions

2.2.4

Fix

  • Fixed version 2.2.4
    pip install --upgrade django==2.2.4

Fix 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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences