When a POST request comes through AJP and the request exceeds the max-post-size limit (maxEntitySize), Undertows AjpServerRequestConduit implementation closes a connection without sending any response to the client/proxy. This behavior results in that a front-end proxy marking the backend worker (application server) as an error state and not forward requests to the worker for a while. In mod_cluster, this continues until the next STATUS request (10 seconds intervals) from the application server updates the server state. So, in the worst case, it can result in All workers are in error state and mod_cluster responds 503 Service Unavailable for a while (up to 10 seconds). In mod_proxy_balancer, it does not forward requests to the worker until the retry timeout passes. However, luckily, mod_proxy_balancer has forcerecovery setting (On by default; this parameter can force the immediate recovery of all workers without considering the retry parameter of the workers if all workers of a balancer are in error state.). So, unlike mod_cluster, mod_proxy_balancer does not result in responding 503 Service Unavailable. An attacker could use this behavior to send a malicious request and trigger server errors, resulting in DoS (denial of service). This flaw was fixed in Undertow 2.2.19.Final, Undertow 2.3.0.Alpha2.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Integration_camel_k | Redhat | - (including) | - (including) |
| Jboss_fuse | Redhat | 7.0.0 (including) | 7.0.0 (including) |
| Undertow | Redhat | * | 2.2.19 (excluding) |
| Undertow | Redhat | 2.3.0-alpha1 (including) | 2.3.0-alpha1 (including) |
| Important: Red Hat JBoss Enterprise Application Platform 7.4.7 Security update | RedHat | undertow | * |
| Red Hat Fuse 7.11.1 | RedHat | undertow | * |
| Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7 | RedHat | eap7-activemq-artemis-0:1.5.5.016-1.redhat_00001.1.ep7.el7 | * |
| Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7 | RedHat | eap7-artemis-native-1:1.5.5.016-1.redhat_00001.1.ep7.el7 | * |
| Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7 | RedHat | eap7-jboss-xnio-base-0:3.5.11-1.Final_redhat_00001.1.ep7.el7 | * |
| Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7 | RedHat | eap7-jsoup-0:1.14.2-1.redhat_00002.1.ep7.el7 | * |
| Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7 | RedHat | eap7-undertow-0:1.4.18-14.SP13_redhat_00001.1.ep7.el7 | * |
| Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7 | RedHat | eap7-wildfly-0:7.1.10-2.GA_redhat_00002.1.ep7.el7 | * |
| Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7 | RedHat | eap7-woodstox-core-0:5.0.3-2.redhat_00002.1.ep7.el7 | * |
| Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7 | RedHat | eap7-xml-security-0:2.0.10-2.redhat_00002.1.ep7.el7 | * |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | RedHat | eap7-jackson-annotations-0:2.10.4-3.redhat_00006.1.el7eap | * |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | RedHat | eap7-jackson-core-0:2.10.4-3.redhat_00006.1.el7eap | * |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | RedHat | eap7-jackson-databind-0:2.10.4-5.redhat_00006.1.el7eap | * |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | RedHat | eap7-jackson-jaxrs-providers-0:2.10.4-3.redhat_00006.1.el7eap | * |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | RedHat | eap7-jackson-modules-base-0:2.10.4-5.redhat_00006.1.el7eap | * |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | RedHat | eap7-jackson-modules-java8-0:2.10.4-2.redhat_00006.1.el7eap | * |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | RedHat | eap7-jboss-server-migration-0:1.7.2-16.Final_redhat_00017.1.el7eap | * |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | RedHat | eap7-netty-0:4.1.63-5.Final_redhat_00003.1.el7eap | * |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | RedHat | eap7-undertow-0:2.0.41-4.SP5_redhat_00001.1.el7eap | * |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | RedHat | eap7-wildfly-0:7.3.14-3.GA_redhat_00002.1.el7eap | * |
| Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7 | RedHat | eap7-wildfly-elytron-0:1.10.17-1.Final_redhat_00001.1.el7eap | * |
| Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8 | RedHat | eap7-undertow-0:2.2.19-1.SP2_redhat_00001.1.el8eap | * |
| Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9 | RedHat | eap7-undertow-0:2.2.19-1.SP2_redhat_00001.1.el9eap | * |
| Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7 | RedHat | eap7-undertow-0:2.2.19-1.SP2_redhat_00001.1.el7eap | * |
| Undertow | Ubuntu | bionic | * |
| Undertow | Ubuntu | focal | * |
| Undertow | Ubuntu | impish | * |
| Undertow | Ubuntu | kinetic | * |
| Undertow | Ubuntu | oracular | * |
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.