GitHub Advisoryadvisory · Maven

GHSA-w6qf-42m7-vh68 Undertow Uncontrolled Resource Consumption Vulnerability

HIGH Published 2024-02-20 Modified 2025-04-28 Official page ↗
Aliases
CVE-2024-1635
Ecosystem
Maven
Packages
io.undertow:undertow-core
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses
CWE-400
Reviewed
2024-09-16

Affected packages

• Maven io.undertow:undertow-core: >= 2.3.0.Final, < 2.3.12.Final → fixed in 2.3.12.Final • Maven io.undertow:undertow-core: < 2.2.31.Final → fixed in 2.2.31.Final

Description

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.

Related

Alias · CVE (1)

  • CVE-2024-1635 A vulnerability was found in Undertow. vulnerability

Weakness · CWE (1)

  • CWE-400 Uncontrolled Resource Consumption weakness

References