VulnerabilityPublished 10 Jul 2024Updated 4 Nov 2025

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

Affects djangoSource CVE Database V5

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

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 1.1% chance of exploitation in 30 days – higher than 67% 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 <5.0.7	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

To mitigate CVE-2024-38875, organizations should prioritize upgrading Django installations to versions 4.2.14 or 5.0.7 or later, where the vulnerability is patched. Until upgrades can be applied, consider implementing input validation or rate limiting on user inputs that are processed by urlize and urlizetrunc functions to prevent excessively large or complex bracketed inputs. Web application firewalls (WAFs) can be configured to detect and block suspicious payloads containing large numbers of brackets. Monitoring application logs for abnormal resource usage or repeated processing of suspicious inputs can help identify attempted exploitation. Additionally, ensure that resource limits (CPU, memory) are enforced at the application or container level to reduce the impact of potential DoS attempts. Regularly review and test incident response plans for availability-related incidents to minimize downtime.

Description

An issue was discovered in Django 4.2 before 4.2.14 and 5.0 before 5.0.7.urlize and urlizetrunc were subject to a potential denial of service attack via certain inputs with a very large number of brackets.

Impact

For European organizations, the primary impact of CVE-2024-38875 is the potential disruption of web services built on vulnerable Django versions. This can lead to denial of service conditions, causing downtime, degraded user experience, and potential loss of business continuity. Critical sectors such as finance, healthcare, government, and e-commerce that rely on Django-based applications could face operational interruptions. Although the vulnerability does not compromise data confidentiality or integrity, the availability impact can indirectly affect trust and compliance with service-level agreements and regulatory requirements like GDPR. Attackers can exploit this vulnerability remotely without authentication, increasing the risk of widespread service outages if exploited at scale. Organizations with public-facing Django applications are particularly vulnerable to automated or targeted DoS attacks leveraging this flaw.

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:13 UTC

WeaknessesCWE-130

Technical details

References

Community reviews

Related threats