CVE-2024-1635

Undertow: out-of-memory error after several closed connections with wildfly-http-client protocol

HIGH
7.5
CVSS Score
Published: February 19, 2024 at 09:23 PM UTC
Updated: October 7, 2026 at 10:17 PM UTC
12 products affected across 3 vendorsActive IQ Unified ManagerOnCommand Workflow AutomationOpenShift Container Platform

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 5%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Vendor states this is fixed in 7.13.0 (unaffected)
Vendor states this is fixed in 0:1.10.17-1.Final_redhat_00001.1.el7eap (unaffected)
Vendor states this is fixed in 0:1.14.2-1.redhat_00002.1.ep7.el7 (unaffected)
Vendor states this is fixed in 0:1.4.18-14.SP13_redhat_00001.1.ep7.el7 (unaffected)
Vendor states this is fixed in 0:1.5.5.016-1.redhat_00001.1.ep7.el7 (unaffected)
Vendor states this is fixed in 0:1.5.5.016-1.redhat_1.1.ep7.el7 (unaffected)
Vendor states this is fixed in 0:1.7.2-16.Final_redhat_00017.1.el7eap (unaffected)
Vendor states this is fixed in 0:2.0.10-2.redhat_00002.1.ep7.el7 (unaffected)
Vendor states this is fixed in 0:2.0.41-4.SP5_redhat_00001.1.el7eap (unaffected)
Vendor states this is fixed in 0:2.10.4-2.redhat_00006.1.el7eap (unaffected)
Vendor states this is fixed in 0:2.10.4-3.redhat_00006.1.el7eap (unaffected)
Vendor states this is fixed in 0:2.10.4-5.redhat_00006.1.el7eap (unaffected)
Vendor states this is fixed in 0:2.2.30-1.SP1_redhat_00001.1.el7eap (unaffected)
Vendor states this is fixed in 0:2.2.30-1.SP1_redhat_00001.1.el8eap (unaffected)
Vendor states this is fixed in 0:2.2.30-1.SP1_redhat_00001.1.el9eap (unaffected)
Vendor states this is fixed in 0:3.5.11-1.Final_redhat_00001.1.ep7.el7 (unaffected)
Vendor states this is fixed in 0:4.1.63-5.Final_redhat_00003.1.el7eap (unaffected)
Vendor states this is fixed in 0:5.0.3-2.redhat_00002.1.ep7.el7 (unaffected)
Vendor states this is fixed in 0:7.1.10-2.GA_redhat_00002.1.ep7.el7 (unaffected)
Vendor states this is fixed in 0:7.3.14-3.GA_redhat_00002.1.el7eap (unaffected)
Vendor states this is fixed in 1:1.5.5.016-1.redhat_00001.1.ep7.el7 (unaffected)
Vendor states this is fixed in 1:1.5.5.016-1.redhat_1.1.ep7.el7 (unaffected)
Vendor states this is fixed in 2.2.30.SP1-redhat-1 (unaffected)
Vendor states this is fixed in 8 (unaffected)
Vendor states this is fixed in 0:18.0.13-1.redhat_00001.1.el7sso (unaffected)
Vendor states this is fixed in 0:18.0.13-1.redhat_00001.1.el8sso (unaffected)
Vendor states this is fixed in 0:18.0.13-1.redhat_00001.1.el9sso (unaffected)
Vendor states this is fixed in 7.6.8 (unaffected)
All versions4
Vendor states this is fixed in 3 (unaffected)
Vendor states this is fixed in 4.4 (unaffected)

References (16)

Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2024:1674
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2024:1675
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2024:1676
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2024:1677
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2024:1860
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2024:1861
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2024:1862
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2024:1864

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHredhat
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-400

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card