Resource Exhaustion Affecting eap7-infinispan-core package, versions <0:11.0.18-2.Final_redhat_00001.1.el7eap


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.04% (15th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Resource Exhaustion vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-EAP7INFINISPANCORE-6565131
  • published5 Apr 2024
  • disclosed27 Oct 2023

Introduced: 27 Oct 2023

CVE-2024-1635  (opens in a new tab)
CWE-400  (opens in a new tab)

How to fix?

Upgrade RHEL:7 eap7-infinispan-core to version 0:11.0.18-2.Final_redhat_00001.1.el7eap or higher.
This issue was patched in RHSA-2024:1674.

NVD Description

Note: Versions mentioned in the description apply only to the upstream eap7-infinispan-core package and not the eap7-infinispan-core package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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.

CVSS Scores

version 3.1