Potential SQL injection via raster lookups on PostGIS
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.0.2, 5.2.11, 4.2.28
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub, 1 Nuclei template
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28. Raster lookups on ``RasterField`` (only implemented on PostGIS) allows remote attackers to inject SQL via the band index parameter. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Tarek Nakkouch for reporting this issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- django
From 6.0 · fixed in 6.0.2; From 5.2 · fixed in 5.2.11; From 4.2 · fixed in 4.2.28
- djangoPyPI
From 6.0a1 · fixed in 6.0.2
- djangoPyPI
From 5.2a1 · fixed in 5.2.11
- djangoPyPI
From 4.2a1 · fixed in 4.2.28
- djangoPyPI
From 4.2 · fixed in 4.2.28; From 5.2 · fixed in 5.2.11; From 6.0 · fixed in 6.0.2