HighGHSA-95rf-557x-44g5CVE-2022-2053

Undertow vulnerable to Dos via Large AJP request

Published 6 Aug 2022 · Updated 8 Nov 2023

Is your project on an affected io.undertow:undertow-core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<2.2.19.Final
Fixed in
2.2.19.Final
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.undertow:undertow-core -DdepVersion=2.2.19.Final -DforceVersion=true
Affected
>=2.3.0.Alpha1 <2.3.0.Alpha2
Fixed in
2.3.0.Alpha2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.undertow:undertow-core -DdepVersion=2.3.0.Alpha2 -DforceVersion=true

Details

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.

Is GHSA-95rf-557x-44g5 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected io.undertow:undertow-core, and gives you the command that fixes it.

More advisories for io.undertow:undertow-core

  • HighCVE-2026-28367Undertow is Vulnerable to HTTP Request/Response Smuggling · 27 Mar 2026
  • HighCVE-2026-28368Undertow is Vulnerable to HTTP Request/Response Smuggling · 27 Mar 2026
  • HighCVE-2026-28369Undertow is Vulnerable to HTTP Request/Response Smuggling · 27 Mar 2026
  • MediumCVE-2026-3260Undertow: Denial of Service via Multipart/Form-Data Parsing on HTTP GET Requests · 24 Mar 2026
  • HighCVE-2024-4027Undertow Servlets Vulnerable to Remote DoS via OutOfMemoryError when Passed Large Parameter Names · 30 Jan 2026
  • CriticalCVE-2025-12543Undertow HTTP server core doesn't properly validate the Host header in incoming HTTP requests · 7 Jan 2026
All 42 advisories for io.undertow:undertow-core

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.