Loading vulnerability…
CVE-2024-53908 is a high-severity SQL injection vulnerability in Django's JSON-field HasKey lookup when used with an Oracle database. Django versions 4.2 before 4.2.17, 5.0 before 5.0.10, and 5.1 before 5.1.4 are affected. The flaw occurs only when django.db.models.fields.json.HasKey is invoked directly and attacker-controlled data is supplied as its left-hand-side value. Django applications using the jsonfield.has_key lookup through double-underscore lookup syntax are not affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Potential SQL injection vulnerability in Django HasKey(lhs, rhs) on Oracle, affecting automation-controller and ansible-lightspeed-container.
The advisory identifies this CVE as addressed, but provides no vulnerability description.
A SQL injection vulnerability in the Django Web Framework involving direct usage of django.db.models.fields.json.HasKey, particularly noted on Oracle.
A high-severity SQL injection vulnerability affecting direct usage of Django's django.db.models.fields.json.HasKey lookup on Oracle when untrusted data is used as the lhs value; applications using jsonfield.has_key through the __ syntax are unaffected.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.