CVE-2022-2053
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Undertow AJP conduit closes connection without response on oversized POST, causing proxy backends to be temporarily marked down, leading to denial of service.
Vulnerability
Overview
CVE-2022-2053 affects Undertow's AJP (Apache JServ Protocol) implementation. When a POST request exceeding the configured max-post-size (maxEntitySize) limit is received, the AjpServerRequestConduit closes the connection without sending any HTTP response to the client or the front-end proxy [1]. This behavior violates the expected protocol handshake, causing the proxy to interpret the backend worker (application server) as unavailable or in error state [2].
Attack
Scenario and Exploitation
An attacker can exploit this by sending a single oversized POST request to an Undertow server behind a load balancer. No authentication is required, as the check occurs before request processing [1]. The proxy will then mark the affected backend worker as down. In deployments using mod_cluster, the worker remains in error state until the next STATUS interval (up to 10 seconds), potentially leading to all workers being marked down and a "503 Service Unavailable" response [1]. In mod_proxy_balancer, the worker is avoided until the configured "retry" timeout passes, but due to the default forcerecovery=On setting, a full DoS is less likely. However, repeated attacks can still degrade performance and availability [1].
Impact
The primary impact is a denial of service (DoS) condition that temporarily prevents the backend from serving requests. The attack is low in complexity and requires no special network position beyond the ability to reach the proxy or load balancer [2]. While the window of unavailability is short (up to 10 seconds), a sustained attack can keep workers in a constant error state, effectively making the application unavailable [1].
Mitigation
Undertow has fixed this issue in versions 2.2.19.Final and 2.3.0.Alpha2 by properly handling the RequestTooBigException and closing the connection cleanly [3][4]. All users are strongly advised to upgrade to these or later versions. No workaround is mentioned in the public advisories, but limiting access to the AJP connector and monitoring for oversized requests can reduce risk [1].
AI Insight generated on May 21, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
io.undertow:undertow-coreMaven | < 2.2.19.Final | 2.2.19.Final |
io.undertow:undertow-coreMaven | >= 2.3.0.Alpha1, < 2.3.0.Alpha2 | 2.3.0.Alpha2 |
Affected products
2- Undertow/Undertowdescription
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
5- github.com/advisories/GHSA-95rf-557x-44g5ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2022-2053ghsaADVISORY
- bugzilla.redhat.com/show_bug.cgighsax_refsource_MISCWEB
- github.com/undertow-io/undertow/pull/1350ghsaWEB
- issues.redhat.com/browse/UNDERTOW-2133ghsax_refsource_MISCWEB
News mentions
0No linked articles in our index yet.