CVE-2020-7471

medium
Published 2020-02-11 ยท Modified 2023-12-06
CVSS v3
โ€”
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
5.5

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.

Predictions

Exploit likelihood
30%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

suse SUSE Affected 1 release
VersionStatusFixed in
โ€” Affected โ€”
arch Arch Fixed 1 release
VersionStatusFixed in
โ€” Fixed 3.0.3-1
debian Debian Fixed 5 releases
VersionStatusFixed in
trixie Fixed 2:2.2.10-1
sid Fixed 2:2.2.10-1
forky Fixed 2:2.2.10-1
bullseye Fixed 2:2.2.10-1
bookworm Fixed 2:2.2.10-1

Package impact

EcosystemPackageVulnerableFixed
python PyPIdjango<1.11.281.11.28
python PyPIdjango>=2.0,<2.2.102.2.10
python PyPIdjango>=3.0,<3.0.33.0.3
python PyPIdjango<eb31d845323618d688ad429479c6dda973056136||>=3.0,<3.0.3eb31d845323618d688ad429479c6dda973056136

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.