SQL injection via interpolated HasKey parameters
Published Dec 6, 2024 · Updated Dec 6, 2024
SQL injection in Django 4.2 before 4.2.17, 5.0 before 5.0.10, and 5.1 before 5.1.4 allows remote attackers to alter Oracle queries. HasKey.as_oracle interpolates collected left-side parameters into JSON_EXISTS SQL, allowing an untrusted lhs value to become SQL text instead of a bound parameter. Exploitation requires direct HasKey construction with an Oracle backend and attacker-controlled lhs data; the ordinary __has_key lookup is unaffected.
Summary
What happened
SQL injection in Django 4.2 before 4.2.17, 5.0 before 5.0.10, and 5.1 before 5.1.4 allows remote attackers to alter Oracle queries. HasKey.as_oracle interpolates collected left-side parameters into JSON_EXISTS SQL, allowing an untrusted lhs value to become SQL text instead of a bound parameter. Exploitation requires direct HasKey construction with an Oracle backend and attacker-controlled lhs data; the ordinary __has_key lookup is unaffected.
The record
- CVE
- CVE-2024-53908
- Published
- Dec 6, 2024
- Updated
- Dec 6, 2024
- Vendor
- Django Software Foundation
- Product
- Django
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 6, 2024CVE publishedPublication date reported by the CVE source.
- Dec 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.2 <4.2.17
- Affected versionversion=5.0 <5.0.10
- Affected versionversion=5.1 <5.1.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo