An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-34265US | critical9.8 | Exploit | ||
An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a k… | ||||
02
references
External citations — patches, advisories, analysis.
- https://docs.djangoproject.com/en/4.0/releases/security/ADVISORY
- https://groups.google.com/forum/#%21forum/django-announceWEB
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HWY6DQWRVBALV73BPUVBXC3QIYUM24IK/WEB
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LTZVAKU5ALQWOKFTPISE257VCVIYGFQI/WEB
- https://nvd.nist.gov/vuln/detail/CVE-2022-34265WEB
- https://security.netapp.com/advisory/ntap-20220818-0006/ADVISORY
- https://www.debian.org/security/2022/dsa-5254ADVISORY
- https://www.djangoproject.com/weblog/2022/jul/04/security-releases/ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan