CVE-2024-53908

Aliases:GHSA-m9g8-fxxm-xg86BIT-django-2024-53908PYSEC-2024-157
Analyzed
Published: 06 Dec 2024, 00:00
Last modified:06 Dec 2024, 16:22

Vulnerability Summary

Overall Risk (default)
high
70/100
CVSS Score
9.8 CRITICAL
v3.1 (cve.org)
EPSS Score
0.86% LOW
1% probability +0.17%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

06 Dec 2024, 00:00
Published
Vulnerability first disclosed
06 Dec 2024, 16:22
Last Modified
Vulnerability information updated

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

CVSS Metrics

  • v4.0CRITICALScore: 9.2CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U
  • v3.1CRITICALScore: 9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 0.86% Percentile: 75%

Techniques & Countermeasures

  • CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

    The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Affected Systems

  • djangoprojectdjango

    ≥ 4.2, < 4.2.17 | ≥ 5.0, < 5.0.10 | ≥ 5.1, < 5.1.4

  • PyPIdjango

    ≥ 5.0.0, < 5.0.10 | ≥ 5.1.0, < 5.1.4 | ≥ 4.2.0, < 4.2.17 | ≥ 5.1, < 5.1.4 | ≥ 5.0, < 5.0.10 | ≥ 4.2, < 4.2.17

References (8)