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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-7471US | critical9.8 | Exploit | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2020/02/03/1WEB
- https://docs.djangoproject.com/en/3.0/releases/security/WEB
- https://github.com/advisories/GHSA-hmr4-m2h5-33qxADVISORY
- https://github.com/django/django/commit/eb31d845323618d688ad429479c6dda973056136FIX
- https://groups.google.com/forum/#!topic/django-announce/X45S86X5bZIWEB
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4A2AP4T7RKPBCLTI2NNQG3T6MINDUUMZ/WEB
- https://seclists.org/bugtraq/2020/Feb/30WEB
- https://security.gentoo.org/glsa/202004-17ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan