CVE-2024-53908GHSA-M9G8-FXXM-XG86BIT-DJANGO-2024-53908PYSEC-2024-157
An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17.
- 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 5.0.10, 5.1.4, 4.2.17
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the django.db.models.fields.json.HasKey lookup, when an Oracle database is used, is subject to SQL injection if untrusted data is used as an lhs value. (Applications that use the jsonfield.has_key lookup via __ are unaffected.)
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- djangoPyPI
From 5.0.0 · fixed in 5.0.10
- djangoPyPI
From 5.1.0 · fixed in 5.1.4
- djangoPyPI
From 4.2.0 · fixed in 4.2.17
- djangoPyPI
From 5.1 · fixed in 5.1.4
- djangoPyPI
From 5.0 · fixed in 5.0.10
- djangoPyPI
From 4.2 · fixed in 4.2.17
- djangoPyPI
From 5.1 · fixed in 5.1.4; From 5.0 · fixed in 5.0.10; From 4.2 · fixed in 4.2.17