Cyber Resilience

CVE-2023-24580

HighDDoS

Published: 15 February 2023

Published
15 February 2023
Modified
18 March 2025
KEV Added
Patch
CVSS Score v3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.1967 95.6th percentile
Risk Priority 27 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2023-24580 is a high-severity Uncontrolled Resource Consumption (CWE-400) vulnerability in Djangoproject Django. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 4.4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

Deeper analysis

CVE-2023-24580 affects the Multipart Request Parser in Django versions 3.2 before 3.2.18, 4.0 before 4.0.10, and 4.1 before 4.1.7. The flaw stems from insufficient limits on multipart form inputs, such as an excessive number of parts, which can trigger uncontrolled resource consumption under CWE-400 and lead to either exhaustion of available file descriptors or memory depletion.

Unauthenticated remote attackers can exploit the issue over the network by submitting specially crafted multipart requests to any Django application endpoint that processes forms. Successful exploitation results in denial of service through resource exhaustion, with no impact on confidentiality or integrity, consistent with the CVSS 7.5 rating.

Django security advisories and the associated release notes direct users to upgrade to the patched versions 3.2.18, 4.0.10, or 4.1.7, which introduce stricter parsing limits. Corresponding package updates have been issued through distribution channels such as Debian LTS and Fedora.

EPSS scores for the CVE rose from lower values to a recorded peak of 0.2541 before receding to the current 0.1967, indicating a period of increased exploitation interest after disclosure. No confirmed reports of in-the-wild exploitation appear in the referenced advisories.

EU & UK References

Vulnerability details

An issue was discovered in the Multipart Request Parser in Django 3.2 before 3.2.18, 4.0 before 4.0.10, and 4.1 before 4.1.7. Passing certain inputs (e.g., an excessive number of parts) to multipart forms could result in too many open files…

more

or memory exhaustion, and provided a potential vector for a denial-of-service attack.

CWE(s)

Related Threats

No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.

Affected Assets

djangoproject
django
3.2 — 3.2.18 · 4.0 — 4.0.10 · 4.1 — 4.1.7
debian
debian linux
10.0

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-400

Limiting concurrent sessions directly prevents uncontrolled resource consumption by capping the number of active sessions per user or account.

addresses: CWE-400

Analysis identifies uncontrolled resource consumption indicative of denial-of-service or abuse attempts.

addresses: CWE-400

Contingency plan testing includes resource exhaustion scenarios to verify recovery, making it harder for attackers to sustain exploits that cause uncontrolled consumption.

addresses: CWE-400

Updated contingency plans include current procedures to detect, contain, and recover from resource exhaustion, limiting an attacker's ability to sustain impact from uncontrolled consumption.

addresses: CWE-400

Alternate site allows resumption of operations if resource exhaustion at the primary site is exploited to cause unavailability.

addresses: CWE-400

Alternate telecommunications services enable resumption of essential functions when primary services become unavailable due to uncontrolled resource consumption.

addresses: CWE-400

The team can analyze and respond to resource exhaustion incidents, reducing the impact of attacks that exploit uncontrolled consumption weaknesses.

addresses: CWE-400

Timely maintenance support and spare parts enable rapid recovery from failures induced by uncontrolled resource consumption, shortening the impact window of denial-of-service attacks.

References