CVE-2024-53908

Description

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.)

Category

9.8
CVSS
Severity: Critical
CVSS 3.1 •
EPSS 0.15%
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://docs.djangoproject.com/en/dev/releases/security/
https://groups.google.com/g/django-announce
https://www.openwall.com/lists/oss-security/2024/12/04/3

Frequently Asked Questions

What is the severity of CVE-2024-53908?
CVE-2024-53908 has been scored as a critical severity vulnerability.
How to fix CVE-2024-53908?
To fix CVE-2024-53908, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2024-53908 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2024-53908 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.