Django 1.11 before 1.11.29, 2.2 before 2.2.11, and 3.0 before 3.0.4 allows SQL Injection if untrusted data is used as a tolerance parameter in GIS functions and aggregates on Oracle. By passing a suitably crafted tolerance to GIS functions and aggregates on Oracle, it was possible to break escaping and inject malicious SQL.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-9402US | high8.8 | — | ||
Django 1.11 before 1.11.29, 2.2 before 2.2.11, and 3.0 before 3.0.4 allows SQL Injection if untrusted data is used as a tolerance parameter in GIS functions and aggregates on Oracl… | ||||
02
references
External citations — patches, advisories, analysis.
- https://docs.djangoproject.com/en/3.0/releases/security/FIX
- https://github.com/advisories/GHSA-3gh2-xw74-jmcwADVISORY
- https://groups.google.com/forum/#%21topic/django-announce/fLUh_pOaKrYWEB
- https://lists.debian.org/debian-lts-announce/2022/05/msg00035.htmlADVISORY
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4A2AP4T7RKPBCLTI2NNQG3T6MINDUUMZ/WEB
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UZMN2NKAGTFE3YKMNM2JVJG7R2W7LLHY/WEB
- https://security.gentoo.org/glsa/202004-17ADVISORY
- https://security.netapp.com/advisory/ntap-20200327-0004/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