Schwachstellen / CVE-2020-7471

kritisch

CVE-2020-7471

django: potential SQL injection via StringAgg(delimiter)

Veröffentlicht Geändert CWE 89
In der Trivy Database seit spätestens 24. Okt. 2026, 07:11 UTCWann der Eintrag vor diesem Build hinzukam, ist nicht erfasst.

Einstufung nach Quelle

NVD9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GHSA9.3CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Red Hat9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Bitnami9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Trivys eigenes Label ist CRITICAL. Kritisch laut NVD, GHSA, Bitnami. Niedriger laut Red Hat (hoch), Ubuntu (mittel).

Beschreibung

Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter (e.g., in Django applications that offer downloads of data as a series of rows with a user-specified column delimiter). By passing a suitably crafted delimiter to a contrib.postgres.aggregates.StringAgg instance, it was possible to break escaping and inject malicious SQL.

Betroffene Pakete und behobene Versionen

QuellePaketBehoben in
bitnami::Bitnami Vulnerability Databasedjango1.11.28, 2.2.10, 3.0.3
pip::GitHub Security Advisory pipdjango1.11.28, 2.2.10, 3.0.3
alpine 3.10py-django1.11.28-r0
alpine 3.11py3-django1.11.28-r0
alpine 3.12py3-django1.11.28-r0
alpine 3.13py3-django1.11.28-r0
alpine 3.14py3-django1.11.28-r0
alpine 3.15py3-django1.11.28-r0
alpine 3.16py3-django1.11.28-r0
alpine 3.17py3-django1.11.28-r0
alpine 3.18py3-django1.11.28-r0
alpine 3.19py3-django1.11.28-r0
Alle 36 Einträge aus 31 Quellen zeigen
QuellePaketBehoben in
bitnami::Bitnami Vulnerability Databasedjango1.11.28, 2.2.10, 3.0.3
pip::GitHub Security Advisory pipdjango1.11.28, 2.2.10, 3.0.3
alpine 3.10py-django1.11.28-r0
alpine 3.11py3-django1.11.28-r0
alpine 3.12py3-django1.11.28-r0
alpine 3.13py3-django1.11.28-r0
alpine 3.14py3-django1.11.28-r0
alpine 3.15py3-django1.11.28-r0
alpine 3.16py3-django1.11.28-r0
alpine 3.17py3-django1.11.28-r0
alpine 3.18py3-django1.11.28-r0
alpine 3.19py3-django1.11.28-r0
alpine 3.20py3-django1.11.28-r0
alpine 3.21py3-django1.11.28-r0
alpine 3.22py3-django1.11.28-r0
alpine 3.23py3-django1.11.28-r0
alpine 3.24py3-django1.11.28-r0
alpine 3.8py-django1.11.28-r0
alpine 3.9py-django1.11.28-r0
alpine edgepy3-django1.11.28-r0
debian 10python-django1:1.11.28-1~deb10u1
debian 11python-django2:2.2.10-1
debian 12python-django2:2.2.10-1
debian 13python-django2:2.2.10-1
debian 14python-django2:2.2.10-1
debian 9python-django1:1.10.7-2+deb9u8
echopython-django2:2.2.10-1
Red Hatpython-djangokein Fix angegeben
Red Hatpython-django-bash-completionkein Fix angegeben
Red Hatpython-django-dockein Fix angegeben
Red Hatpython2-djangokein Fix angegeben
Red Hatpython2-django-dockein Fix angegeben
Red Hatpython3-djangokein Fix angegeben
ubuntu 18.04python-django1:1.11.11-1ubuntu1.7
ubuntu 18.04-ESMpython-django1:1.11.11-1ubuntu1.7
ubuntu 19.10python-django1:1.11.22-1ubuntu1.2

Referenzen

Alle 28 Referenzen

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.