Resource exhaustion in Django
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-24580US | high7.5 | — | ||
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 p… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2023/02/14/1WEB
- https://docs.djangoproject.com/en/4.1/releases/securityWEB
- https://github.com/django/djangoPACKAGE
- https://github.com/django/django/commit/628b33a854a9c68ec8a0c51f382f304a0044ec92WEB
- https://github.com/django/django/commit/83f1ea83e4553e211c1c5a0dfc197b66d4e50432WEB
- https://github.com/django/django/commit/a665ed5179f5bbd3db95ce67286d0192eff041d8WEB
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2023-13.yamlWEB
- https://groups.google.com/forum/#!forum/django-announceWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan