Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection
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/securityWEB
- https://github.com/advisories/GHSA-p64x-8rxx-wf6qADVISORY
- https://github.com/django/djangoPACKAGE
- https://github.com/django/django/commit/0dc9c016fadb71a067e5a42be30164e3f96c0492WEB
- https://github.com/django/django/commit/5e2f4ddf2940704a26a4ac782b851989668d74dbWEB
- https://github.com/django/django/commit/877c800f255ccaa7abde1fb944de45d1616f5cc9WEB
- https://github.com/django/django/commit/a9010fe5555e6086a9d9ae50069579400ef0685eWEB
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2022-213.yamlWEB
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