CVE-2023-24580
HighResource exhaustion in Django
Published Feb 15, 2023 · Updated Oct 8, 2026 · Also known as BIT-django-2023-24580, DEBIAN-CVE-2023-24580, DLA-3329-1, GHSA-2hrw-hx67-34x6, PYSEC-2023-13, SUSE-SU-2023:0704-1, SUSE-SU-2023:2080-1, UBUNTU-CVE-2023-24580, USN-5868-1
Key Facts
Patch immediately- CVE-2023-24580 is a high-severity vulnerability (CVSS 8.7 v4) affecting Django (Djangoproject), Debian Linux, py3-django (alpine) and 22 more products.
- It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
- EPSS estimates a 63% probability of exploitation in the next 30 days.
- Fixed versions are available, including automation-controller 0:4.4.2-1.el8ap, automation-controller 0:4.4.2-1.el9ap, Django 3.2.18.
- Brandefense priority: patch immediately, because it is very likely to be exploited soon.
CVSS v4
8.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
EPSS (30-day exploit likelihood)
63%
Higher than 99.1% of all scored CVEs
Exploited in the wild
No known
Not in a known-exploited catalog
Public exploit code
None known
Get the full CVE-2023-24580 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
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 or memory exhaustion, and provided a potential vector for a denial-of-service attack.
Affected Products
67 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| DjangoDjangoproject | >= 3.2.0, >= 3.2a1, >= 4.0a1 | 3.2.18 |
| Debian LinuxDebian | 10.0 | n/a |
| py3-djangoalpine | See advisory | 3.2.18-r0 |
| python-Djangodebian | See advisory | 2:2.2.28-1~deb11u2 |
| automation-controllerredhat | See advisory | 0:4.4.2-1.el8ap |
Patched Releases
automation-controller
0:4.4.2-1.el8ap, 0:4.4.2-1.el9ap
Django
3.2.18, 4.0.10, 4.1.7
libsolv
0.7.20-6.el8+sp999
py3-django
3.2.18-r0
python-Django
0:3.2.18-1.0.1.el8ui, 1:1.11.11-1ubuntu1.20, 1:1.11.29-1+deb10u7, 2:2.2.12-1ubuntu0.16, 2:2.2.28-1~deb11u2, 2:3.2.12-2ubuntu1.5, 3:3.2.18-1, 1.11.15-2.1, 1.11.29-3.45.1
python-Django1
1.11.29-3.44.1
python-jinja2
2.7.2-4.el7+sp999
python3-Django
2.2.28-bp154.2.9.1
python3-Django1
1.11.29-bp154.2.3.1
python310-Django
4.1.7-1.1
python310-Django4
4.2.14-1.1
python311-Django
5.1.5-1.1
python311-Django4
4.2.14-1.1
python312-Django
5.1.5-1.1
python312-Django4
4.2.14-1.1
python312-Django6
6.0-1.1
python313-Django
5.1.5-1.1
python313-Django4
4.2.30-4.1
python313-Django5
5.2.16-1.1
python313-Django6
6.0-1.1
python314-Django4
4.2.30-4.1
python314-Django5
5.2.16-1.1
python38-Django
4.1.7-1.1
python39-Django
4.1.7-1.1
seal-libsolv
0.7.20-6.el8+sp999
Timeline
Publicly disclosed
Feb 15, 2023
Last updated
Oct 8, 2026
Weakness Type
- CWE-400 Uncontrolled Resource Consumption
References
- advisoryRHSA-2023:2097
- advisoryRHSA-2023:2101
- advisoryRHSA-2023:4692
- advisoryhttps://bugzilla.suse.com/1208082
- advisoryGHSA advisory
FAQ
Common Questions.
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.
Affected: Django (Djangoproject) versions >= 3.2.0, >= 3.2a1, >= 4.0a1; Debian Linux versions 10.0; py3-django (alpine), among others. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including automation-controller 0:4.4.2-1.el8ap, automation-controller 0:4.4.2-1.el9ap, Django 3.2.18.
Brandefense priority: patch immediately, because it is very likely to be exploited soon.
Is CVE-2023-24580 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo