Cyber Resilience

CVE-2024-39614

Djangoproject Django 4.2 – 4.2.14

Published
10 July 2024
Modified
04 November 2025
Patch / advisory
View advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.29 98th percentile
Risk Priority 73 floored blend · peak EPSS

Summary

CVE-2024-39614 is a high-severity Improper Handling of Length Parameter Inconsistency (CWE-130) vulnerability in Djangoproject Django. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-39614 affects the get_supported_language_variant() function in Django versions 5.0 before 5.0.7 and 4.2 before 4.2.14. The flaw, assigned CWE-130, allows a denial-of-service condition when the function processes very long input strings containing specific characters, resulting in a CVSS 7.5 rating driven entirely by high availability impact over the network without authentication.

An unauthenticated remote attacker can supply a crafted, excessively long language-variant string to any Django application code path that invokes this function, triggering excessive resource consumption and service disruption. No privileges or user interaction are required, making the attack surface broad for any exposed Django deployment that uses internationalization features.

Official Django security advisories and release notes direct users to upgrade immediately to 5.0.7 or 4.2.14, which contain the fix; the project’s announcement channels and documentation pages provide the corresponding patch details and upgrade guidance.

EPSS scores have remained low and essentially flat near 0.07, with no indication of emerging exploitation interest.

EU & UK References

Vulnerability Data

An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. get_supported_language_variant() was subject to a potential denial-of-service attack when used with very long strings containing specific characters.

CWE(s)
CWE-130

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-38875Same product: Djangoproject Django
CVE-2024-41990Same product: Djangoproject Django
CVE-2026-5766Same product: Djangoproject Django
CVE-2024-41991Same product: Djangoproject Django
CVE-2026-53877Same product: Djangoproject Django
CVE-2024-45230Same product: Djangoproject Django
CVE-2026-4292Same product: Djangoproject Django
CVE-2026-4277Same product: Djangoproject Django
CVE-2022-34265Same product: Djangoproject Django
CVE-2025-13372Same product: Djangoproject Django

Affected Assets

djangoproject
django
4.2 — 4.2.14 · 5.0 — 5.0.7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.5.5
  • V4.2.1
  • V4.2.2

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover length-parameter inconsistencies through targeted parsing tests.

SI-10 Information Input Validation good match

Input validation enforces correct length-to-data consistency checks on parsed messages before processing.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce length validation and input sanitization during coding and review.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect length-inconsistency vulnerabilities before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and length checks that directly address inconsistent length fields.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit rules for handling message lengths and data structures.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles require robust parsing and bounds checking to prevent length-related flaws.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit improper length handling and enforce defensive parsing practices.

References