CVE Vulnerabilities

CVE-2023-24580

Uncontrolled Resource Consumption

Published: Feb 15, 2023 | Modified: Mar 18, 2025
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
7.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

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.

Weakness

The product does not properly control the allocation and maintenance of a limited resource.

Affected Software

NameVendorStart VersionEnd Version
DjangoDjangoproject3.2 (including)3.2.18 (excluding)
DjangoDjangoproject4.0 (including)4.0.10 (excluding)
DjangoDjangoproject4.1 (including)4.1.7 (excluding)
Red Hat Ansible Automation Platform 2.4 for RHEL 8RedHatautomation-controller-0:4.4.2-1.el8ap*
Red Hat Ansible Automation Platform 2.4 for RHEL 9RedHatautomation-controller-0:4.4.2-1.el9ap*
Red Hat Satellite 6.13 for RHEL 8RedHatpython-django-0:3.2.18-1.el8pc*
Red Hat Satellite 6.13 for RHEL 8RedHatpython-django-0:3.2.18-1.el8pc*
RHUI 4 for RHEL 8RedHatpython-django-0:3.2.18-1.0.1.el8ui*
Python-djangoUbuntubionic*
Python-djangoUbuntudevel*
Python-djangoUbuntuesm-infra-legacy/trusty*
Python-djangoUbuntuesm-infra/bionic*
Python-djangoUbuntuesm-infra/focal*
Python-djangoUbuntuesm-infra/xenial*
Python-djangoUbuntufocal*
Python-djangoUbuntujammy*
Python-djangoUbuntukinetic*
Python-djangoUbuntulunar*
Python-djangoUbuntumantic*
Python-djangoUbuntunoble*
Python-djangoUbuntuoracular*
Python-djangoUbuntuplucky*
Python-djangoUbuntuquesting*
Python-djangoUbuntutrusty*
Python-djangoUbuntutrusty/esm*
Python-djangoUbuntuupstream*
Python-djangoUbuntuxenial*

Potential Mitigations

  • Mitigation of resource exhaustion attacks requires that the target system either:

  • The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.

  • The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.

References