HighGHSA-w6qf-42m7-vh68CVE-2024-1635

Undertow Uncontrolled Resource Consumption Vulnerability

Published 20 Feb 2024 · Updated 28 Apr 2025

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.3.0.Final <2.3.12.Final
Fixed in
2.3.12.Final
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.undertow:undertow-core -DdepVersion=2.3.12.Final -DforceVersion=true
Affected
<2.2.31.Final
Fixed in
2.2.31.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.31.Final -DforceVersion=true

Details

A vulnerability was found in Undertow. This vulnerability impacts a server that supports the wildfly-http-client protocol. Whenever a malicious user opens and closes a connection with the HTTP port of the server and then closes the connection immediately, the server will end with both memory and open file limits exhausted at some point, depending on the amount of memory available.

At HTTP upgrade to remoting, the WriteTimeoutStreamSinkConduit leaks connections if RemotingConnection is closed by Remoting ServerConnectionOpenListener. Because the remoting connection originates in Undertow as part of the HTTP upgrade, there is an external layer to the remoting connection. This connection is unaware of the outermost layer when closing the connection during the connection opening procedure. Hence, the Undertow WriteTimeoutStreamSinkConduit is not notified of the closed connection in this scenario. Because WriteTimeoutStreamSinkConduit creates a timeout task, the whole dependency tree leaks via that task, which is added to XNIO WorkerThread. So, the workerThread points to the Undertow conduit, which contains the connections and causes the leak.

Is GHSA-w6qf-42m7-vh68 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.