In PHP 8.0.X before 8.0.28, 8.1.X before 8.1.16 and 8.2.X before 8.2.3, excessive number of parts in HTTP form upload can cause high resource consumption and excessive number of log entries. This can cause denial of service on the affected server by exhausting CPU resources or disk space.
The product does not properly control the allocation and maintenance of a limited resource.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Php | Php | 8.0.0 (including) | 8.0.28 (excluding) |
Php | Php | 8.1.0 (including) | 8.1.16 (excluding) |
Php | Php | 8.2.0 (including) | 8.2.3 (excluding) |
Red Hat Enterprise Linux 8 | RedHat | php:8.0-8080020231006102311.0b4eb31d | * |
Red Hat Enterprise Linux 9 | RedHat | php-0:8.0.30-1.el9_2 | * |
Red Hat Enterprise Linux 9 | RedHat | php:8.1-9030020231221080340.9 | * |
Php5 | Ubuntu | esm-infra-legacy/trusty | * |
Php5 | Ubuntu | trusty | * |
Php5 | Ubuntu | trusty/esm | * |
Php7.0 | Ubuntu | esm-infra/xenial | * |
Php7.0 | Ubuntu | xenial | * |
Php7.2 | Ubuntu | bionic | * |
Php7.2 | Ubuntu | esm-infra/bionic | * |
Php7.4 | Ubuntu | esm-infra/focal | * |
Php7.4 | Ubuntu | focal | * |
Php8.1 | Ubuntu | jammy | * |
Php8.1 | Ubuntu | kinetic | * |
Php8.1 | Ubuntu | lunar | * |
Php8.1 | Ubuntu | upstream | * |
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.