VulnerabilityPublished 10 Jul 2024Updated 4 Nov 2025

CVE-2024-39614: django · Improper Handling of Length Parameter Inconsistency

Affects djangoSource CVE Database V5

Not known to be exploited · 28% EPSS · CVSS 7.5 High : upgrade to 5.0.7 or 4.2.14 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 28.6% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.0.7, 4.2.14

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade django to 5.0.7 or 4.2.14.

Affected software

Product	Affected	Fixed in
PyPIdjango`pkg:pypi/django`Other threats	Affected <4.2.14 >=4.2 <5.0.7 >=5.0	Fixed in 4.2.14 5.0.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately assess their Django deployments to identify versions prior to 5.0.7 and 4.2.14. The primary mitigation is to upgrade affected Django instances to the patched versions 5.0.7 or 4.2.14 or later. Where immediate upgrading is not feasible, organizations should implement input validation and length checks on language-related inputs to limit excessively long strings and filter out suspicious characters that could trigger the vulnerability. Deploying web application firewalls (WAFs) with custom rules to detect and block anomalous requests targeting language headers or parameters can provide temporary protection. Monitoring application logs for unusual spikes in resource usage or malformed language inputs can help detect attempted exploitation. Additionally, organizations should review their incident response plans to prepare for potential DoS events and ensure capacity planning accounts for sudden load increases. Regularly updating dependencies and maintaining a robust patch management process will reduce exposure to similar vulnerabilities.

Description

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.

Impact

For European organizations, this vulnerability primarily threatens the availability of web applications built on affected Django versions. Organizations operating critical online services, e-commerce platforms, or public-facing portals using these Django versions may experience service disruptions or outages if attackers exploit this DoS vulnerability. The impact is particularly significant for sectors relying on continuous availability, such as finance, healthcare, government, and telecommunications. Since the vulnerability does not affect confidentiality or integrity, data breaches are unlikely; however, denial-of-service conditions can lead to reputational damage, loss of customer trust, and potential financial losses due to downtime. The ease of exploitation without authentication increases the risk, especially for organizations with high traffic volumes or those exposed directly to the internet. Additionally, the lack of known exploits in the wild currently provides a window for proactive mitigation before widespread attacks occur.

CWE-130Improper Handling of Length Parameter Inconsistency (opens in a new tab)
Base weakness
The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data.
Implementation
When processing structured incoming data containing a size field followed by raw data, ensure that you identify and resolve any inconsistencies between the size field and the actual size of the data.
Implementation
Do not let the user control the size of the buffer.
Implementation
Validate that the length of the user-supplied data is consistent with the buffer size.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Buffer Overflow via Parameter Expansion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 17:15 UTC

WeaknessesCWE-130

Technical details

References

Community reviews

Related threats