A vulnerability was found under the scope of Undertow. This vulnerability impacts a server that supports the wildfly-http-client protocol. Whenever a malicious user opens and close a connection with the HTTP port of the server and close the connection immediately, the server will end with both memory and open files limits exhausted at some point, depending on the amount of memory available. At Http upgrade to remoting, WriteTimeoutStreamSinkConduit leaks connections if RemotingConnection is closed by Remoting ServerConnectionOpenListener Because the remoting connection originates in Undertow as part of the HTTP upgrade, we have an external layer to the remoting connection. This connection is unaware of the outermost layer when closing the connection during connection opening procedure, and hence the Undertow WriteTimeoutStreamSinkConduit is not notified of the connection being closed in this scenario. Because WriteTimeoutStreamSinkConduit creates a timeout task, the whole dependency tree leaks via that task, that is added to XNIO WorkerThread. So, the workerThread points to the Undertow conduit, that contains the connections and causes the leak.
Is there information on the the upstream status for undertow? Is there an upstream issue and/or fixing commit available?
@carnil: Please follow up with https://issues.redhat.com/browse/WFLY-18700 and linked issues.
This comment was flagged a spam, view the edit history to see the original text if required.
Marking EAP-8 as not affected because EAP 8 GA was released with the fixed version.
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9 Via RHSA-2024:1676 https://access.redhat.com/errata/RHSA-2024:1676
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8 Via RHSA-2024:1675 https://access.redhat.com/errata/RHSA-2024:1675
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7 Via RHSA-2024:1674 https://access.redhat.com/errata/RHSA-2024:1674
This issue has been addressed in the following products: EAP 7.4.16 Via RHSA-2024:1677 https://access.redhat.com/errata/RHSA-2024:1677
This issue has been addressed in the following products: Red Hat Single Sign-On 7.6 for RHEL 7 Via RHSA-2024:1860 https://access.redhat.com/errata/RHSA-2024:1860
This issue has been addressed in the following products: Red Hat Single Sign-On 7.6 for RHEL 8 Via RHSA-2024:1861 https://access.redhat.com/errata/RHSA-2024:1861
This issue has been addressed in the following products: Red Hat Single Sign-On 7.6 for RHEL 9 Via RHSA-2024:1862 https://access.redhat.com/errata/RHSA-2024:1862
This issue has been addressed in the following products: RHEL-8 based Middleware Containers Via RHSA-2024:1864 https://access.redhat.com/errata/RHSA-2024:1864
This issue has been addressed in the following products: RHSSO 7.6.8 Via RHSA-2024:1866 https://access.redhat.com/errata/RHSA-2024:1866