First published: Thu Jun 30 2022(Updated: )
A flaw was found in Django. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/python-django | <0:3.2.14-2.el8 | 0:3.2.14-2.el8 |
redhat/python-django | <0:3.2.14-3.el8 | 0:3.2.14-3.el8 |
debian/1:1.10.7-2+deb9u17 | ||
debian/2:2.2.26-1 | ||
debian/2:3.2.13-1 | ||
Djangoproject Django | >=3.2<3.2.14 | |
Djangoproject Django | >=4.0<4.0.6 | |
debian/python-django | <=1:1.11.29-1~deb10u1 | 1:1.11.29-1+deb10u10 2:2.2.28-1~deb11u2 3:3.2.19-1+deb12u1 3:3.2.21-1 3:4.2.8-1 |
redhat/python-django | <4.0.6 | 4.0.6 |
redhat/python-django | <3.2.14 | 3.2.14 |
pip/Django | >=4.0a1<4.0.6 | 4.0.6 |
pip/Django | >=3.2a1<3.2.14 | 3.2.14 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-34265 is a vulnerability in Django 3.2 before 3.2.14 and 4.0 before 4.0.6 that allows for SQL injection if untrusted data is used as a kind/lookup_name value in the Trunc() and Extract() database functions.
CVE-2022-34265 has a severity rating of 9.8 (Critical).
CVE-2022-34265 affects Django 3.2 before 3.2.14 and 4.0 before 4.0.6.
To fix CVE-2022-34265, update your Django installation to version 3.2.14 or 4.0.6 depending on your current version.
You can find more information about CVE-2022-34265 on the Debian Security Tracker, the Debian bug report, and the NIST vulnerability database.