SQL injection in Django
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| django PyPI |
|
|
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.
From the CVE record · mitre
Affected Django versions can fail to escape an untrusted delimiter passed to contrib.postgres.aggregates.StringAgg. An attacker who can supply that delimiter can inject malicious SQL; the input does not specify whether authentication is required.
Engineers running the PyPI django package on Django 1.11 before 1.11.28, 2.2 before 2.2.10, or 3.0 before 3.0.3 should check their applications.