CVE-2020-7471 — SQL Injection in Django
Severity
9.8CRITICALNVD
EPSS
9.4%
top 7.19%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
Timeline
PublishedFeb 3
Latest updateFeb 11
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitability: 3.9 | Impact: 5.9
Affected Packages2 packages
Patches
🔴Vulnerability Details
4📋Vendor Advisories
3💬Community
6Bugzilla▶
CVE-2020-7471 python-django: django: potential SQL injection via StringAgg(delimiter) [openstack-rdo]↗2020-02-05
Bugzilla▶
CVE-2020-7471 python-django: django: potential SQL injection via StringAgg(delimiter) [epel-8]↗2020-02-05
Bugzilla▶
CVE-2020-7471 python-django: django: potential SQL injection via StringAgg(delimiter) [epel-7]↗2020-02-05
Bugzilla▶
CVE-2020-7471 django:1.6/python-django: django: potential SQL injection via StringAgg(delimiter) [fedora-all]↗2020-02-05