published 3 Feb 2020 · updated 4 Aug 2024
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…
6.0MediumEPSS 66%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 66%. No fixed version is recorded.
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.
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket