Vulnerability advisory
CVE-2022-34265
Also known as BIT-django-2022-34265GHSA-p64x-8rxx-wf6qPYSEC-2022-213
Severity
Severity not reported.
Affected versions
Repository
| Affected commits | Fixed by commit |
|---|---|
| GIT github.com/django/django ↗ | |
| 3591e1c1acbd7c13174275367c3fdf012cb0413b to before 746e88cc634469112b823225c19d75c7362f8ecf | 746e88cc634469112b823225c19d75c7362f8ecf |
| ef62a3a68c9d558486145a42c0d71ea9a76add9e to before caad462feaa84ba78ed658a9595a4a4363dad2db | caad462feaa84ba78ed658a9595a4a4363dad2db |
Description
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.
References
- Webdocs.djangoproject.com/en/4.0/releases/security/ ↗
- Webgroups.google.com/forum/#%21forum/django-announce ↗
- Advisorygithub.com/CVEProject/cvelistV5/tree/main/cves/2022/34xxx/CVE-2022-34265.json ↗
- Advisorylists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HWY6DQWRVBALV73BPUVBXC3QIYUM24IK/ ↗
- Advisorylists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LTZVAKU5ALQWOKFTPISE257VCVIYGFQI/ ↗
- Advisorynvd.nist.gov/vuln/detail/CVE-2022-34265 ↗
- Advisorysecurity.netapp.com/advisory/ntap-20220818-0006/ ↗
- Advisorywww.debian.org/security/2022/dsa-5254 ↗
- ARTICLEwww.djangoproject.com/weblog/2022/jul/04/security-releases/ ↗