Vulnerability advisory

PYSEC-2020-35

Published Feb 3, 2020Updated Dec 6, 2023OSV record ↗

Also known as BIT-django-2020-7471CVE-2020-7471GHSA-hmr4-m2h5-33qx

Severity

Severity not reported.

Affected versions

django PyPI

Affected	Fixed
GIT github.com/django/django ↗
All commits before eb31d845323618d688ad429479c6dda973056136	Commit `eb31d845323618d688ad429479c6dda973056136`
`1.11` to before 1.11.28	`1.11.28`Advisories →
`2.2` to before 2.2.10	`2.2.10`Advisories →
`3.0` to before 3.0.3	`3.0.3`Advisories →
Also listed as affected (40) `1.11` `1.11.1` `1.11.2` `1.11.3` `1.11.4` `1.11.5` `1.11.6` `1.11.7` `1.11.8` `1.11.9` `1.11.10` `1.11.11` `1.11.12` `1.11.13` `1.11.14` `1.11.15` `1.11.16` `1.11.17` `1.11.18` `1.11.20` `1.11.21` `1.11.22` `1.11.23` `1.11.24` `1.11.25` `1.11.26` `1.11.27` `2.2` `2.2.1` `2.2.2` `2.2.3` `2.2.4` `2.2.5` `2.2.6` `2.2.7` `2.2.8` `2.2.9` `3.0` `3.0.1` `3.0.2`

Description

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.

PYSEC-2020-35

Affected versions

django PyPI

Description

References