CVE-2024-1635: Undertow: out-of-memory error after several closed connections with wildfly-http-client protocol
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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-1635 is a denial-of-service issue in Undertow when servers support the wildfly-http-client protocol. An unauthenticated network user can cause memory and open file handles to be exhausted, potentially taking application services offline. The issue is availability-focused; the provided sources do not indicate data theft or tampering.
Executive priority
Treat as a high-priority availability risk for business-critical Java application servers. Prioritize externally reachable or high-traffic JBoss EAP/Undertow services. If affected systems are internal and monitored, schedule rapid patching through normal change control; if exposed, accelerate remediation and add monitoring.
Technical view
During HTTP upgrade to remoting, Undertow’s WriteTimeoutStreamSinkConduit can retain timeout tasks after a remoting connection is closed during opening. XNIO worker threads then keep references to the conduit and connection tree, causing memory and file descriptor leaks. CVSS is 7.5, network exploitable, low complexity, no privileges, availability impact only.
Likely exposure
Exposure is most likely on internet- or network-reachable Undertow/JBoss EAP services with the wildfly-http-client protocol enabled. The source bundle lists affected Red Hat JBoss Enterprise Application Platform packages and related Red Hat advisories. Non-Red Hat Undertow deployments need vendor or dependency validation because fixed version details are incomplete here.
Exploitation context
The CVE is not listed as CISA KEV in the provided data, and no cited source states active exploitation. Abuse requires reaching the server HTTP port and triggering the vulnerable connection lifecycle repeatedly. The business impact is service degradation or outage from resource exhaustion.
Researcher notes
This is CWE-400 resource consumption caused by a lifecycle cleanup gap around Undertow remoting upgrade handling. The source bundle provides strong Red Hat product/advisory signals but limited upstream fixed-version detail. Do not assume active exploitation without additional evidence; focus validation on reachable protocol support and package advisory status.
Mitigation direction
Apply the relevant Red Hat security advisories for affected JBoss EAP packages.
Check vendor guidance for non-Red Hat Undertow or bundled Undertow deployments.
Limit network exposure of affected HTTP endpoints where business requirements allow.
Monitor memory and file descriptor usage until updates are deployed.
Review whether wildfly-http-client protocol support is required on exposed services.
Validation and detection
Inventory applications using Undertow, WildFly, or Red Hat JBoss EAP.
Map installed package versions to Red Hat CVE and errata applicability.
Confirm whether the wildfly-http-client protocol is enabled or reachable.
Check logs and metrics for unexplained memory or file descriptor growth.
Verify patched advisory levels after maintenance is completed.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.