First published: Fri Jun 10 2022(Updated: )
When a POST request comes through AJP and the request exceeds the max-post-size limit (maxEntitySize), Undertow's 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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/eap7-undertow | <0:2.2.19-1.SP2_redhat_00001.1.el8ea | 0:2.2.19-1.SP2_redhat_00001.1.el8ea |
redhat/eap7-undertow | <0:2.2.19-1.SP2_redhat_00001.1.el9ea | 0:2.2.19-1.SP2_redhat_00001.1.el9ea |
redhat/eap7-undertow | <0:2.2.19-1.SP2_redhat_00001.1.el7ea | 0:2.2.19-1.SP2_redhat_00001.1.el7ea |
Redhat Integration Camel K | ||
Redhat Jboss Fuse | =7.0.0 | |
Redhat Undertow | <2.2.19 | |
Redhat Undertow | =2.3.0-alpha1 | |
redhat/undertow | <2.2.19. | 2.2.19. |
redhat/undertow | <2.3.0. | 2.3.0. |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2022-2053 is a vulnerability in Undertow that allows an attacker to send a malicious request to the server, potentially resulting in denial of service.
CVE-2022-2053 allows an attacker to exploit a flaw in Undertow's AjpServerRequestConduit implementation to close a connection without sending any response to the client/proxy, resulting in a potential denial of service.
CVE-2022-2053 has a severity rating of high (7 out of 10).
To fix CVE-2022-2053, it is recommended to update Undertow to version 2.2.19 or 2.3.0, depending on the affected software.
You can find more information about CVE-2022-2053 in the following references: [Reference 1](https://access.redhat.com/errata/RHSA-2022:6823), [Reference 2](https://access.redhat.com/errata/RHSA-2022:6821), [Reference 3](https://access.redhat.com/errata/RHSA-2022:6822).