BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-53908High confidence

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

Unknown · Unknown

9.8CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 1.42% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

8 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · communitypy3-djangoVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.4.2.20-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · communitypy3-djangoVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.4.2.20-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.21v3.21 · communitypy3-djangoVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.4.2.20-r0Alpine Security Database ↗Source updated 19 Aug 2026
Debian trixietrixie · sourcepython-djangoVendor fix publishedDebian records a fixed source-package version for this release.3:4.2.17-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcepython-djangoNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcepython-djangoVendor fix publishedDebian records a fixed source-package version for this release.3:4.2.17-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcepython-djangoVendor fix publishedDebian records a fixed source-package version for this release.3:4.2.17-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivepython-djangoVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.3:4.2.11-1ubuntu1.4Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges12 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
PyPIdjangoECOSYSTEM: introduced 5.0.0; fixed 5.0.105.0.10OSV record ↗aggregator derived · 10 Sep 2026
PyPIdjangoECOSYSTEM: introduced 5.1.0; fixed 5.1.45.1.4OSV record ↗aggregator derived · 10 Sep 2026
PyPIdjangoECOSYSTEM: introduced 4.2.0; fixed 4.2.174.2.17OSV record ↗aggregator derived · 10 Sep 2026
PyPIdjangoECOSYSTEM: introduced 5.1; fixed 5.1.45.1.4OSV record ↗aggregator derived · 10 Sep 2026
PyPIdjangoECOSYSTEM: introduced 5.0; fixed 5.0.105.0.10OSV record ↗aggregator derived · 10 Sep 2026
PyPIdjangoECOSYSTEM: introduced 4.2; fixed 4.2.174.2.17OSV record ↗aggregator derived · 10 Sep 2026
pipDjango>= 5.0.0, < 5.0.105.0.10GitHub advisory ↗github reviewed aggregator · 14 Jan 2025
pipDjango>= 5.1.0, < 5.1.45.1.4GitHub advisory ↗github reviewed aggregator · 14 Jan 2025
pipDjango>= 4.2.0, < 4.2.174.2.17GitHub advisory ↗github reviewed aggregator · 14 Jan 2025
pipdjango>= 5.1, < 5.1.45.1.4GitHub advisory ↗github reviewed aggregator · 14 Jan 2025
pipdjango>= 5.0, < 5.0.105.0.10GitHub advisory ↗github reviewed aggregator · 14 Jan 2025
pipdjango>= 4.2, < 4.2.174.2.17GitHub advisory ↗github reviewed aggregator · 14 Jan 2025
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-53908 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitydjango: Potential SQL injection in HasKey(lhs, rhs) on Oracle
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • ansible-tower.src as a component of Red Hat Ansible Automation Platform 1.2
  • ansible-automation-platform-24/lightspeed-rhel8 as a component of Red Hat Ansible Automation Platform 2
  • ansible-automation-platform-24/platform-resource-runner-rhel8 as a component of Red Hat Ansible Automation Platform 2
  • ansible-automation-platform-25/ansible-dev-tools-rhel9 as a component of Red Hat Ansible Automation Platform 2
  • ansible-automation-platform-25/platform-resource-runner-rhel9 as a component of Red Hat Ansible Automation Platform 2
Summary
A vulnerability was found in the Django Web Framework. The direct usage of django.db.models.fields.json.HasKey may be vulnerable to SQL injection if untrusted data is used to perform queries.
Remediation
Red Hat Ansible Automation Platform
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-0049

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

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

What

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

Why

Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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

Why

Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-89 ↗

CWE-89: Improper 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.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-89
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-3609Django: Mehrere Schwachstellen

Ein anonymer Angreifer kann mehrere Schwachstellen in Django ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder Daten zu manipulieren.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241211Security Bulletin 11 Dec 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 11 Dec 2024, published on 11 December 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-024842Django Software Foundation の Django における SQL インジェクションの脆弱性

Django Software Foundation の Django には、SQL インジェクションの脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
Red Hat Ansible Automation Platform
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

  • django-announce - Google Groups →Original publisher ↗Searchable text snapshot · Captured 27 Sep 2026Groups Groups Conversations All groups and messages Send feedback to Google Help Training Sign in Groups Groups Conversations About 1–30 of 347     Mark all as read Report group 0 selected   Jacob Walls Sep 2 Django bugfix release issued: 6.1.1 Details are available on the Django project weblog: https://w
04

Evidence and provenance

Published 6 Dec 2024 · Last source change 6 Dec 2024, 16:22 UTC · CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVE recordCVE.org · 5.1
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-0049
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCISA ADP
NVD statusNVD enriched

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    n/a · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    n/a · Fixed: Red Hat Ansible Automation Platform
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2024-0049↗Red Hat Product Security security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-53908 · cve.blacktree.nl