Bug 2260840 (CVE-2024-1023) - CVE-2024-1023 io.vertx/vertx-core: memory leak due to the use of Netty FastThreadLocal data structures in Vertx
Summary: CVE-2024-1023 io.vertx/vertx-core: memory leak due to the use of Netty FastTh...
Keywords:
Status: NEW
Alias: CVE-2024-1023
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2260857
TreeView+ depends on / blocked
 
Reported: 2024-01-29 11:01 UTC by TEJ RATHI
Modified: 2024-06-13 18:16 UTC (History)
90 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A vulnerability in the Eclipse Vert.x toolkit results in a memory leak due to using Netty FastThreadLocal data structures. Specifically, when the Vert.x HTTP client establishes connections to different hosts, triggering the memory leak. The leak can be accelerated with intimate runtime knowledge, allowing an attacker to exploit this vulnerability. For instance, a server accepting arbitrary internet addresses could serve as an attack vector by connecting to these addresses, thereby accelerating the memory leak.
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2024:1662 0 None None None 2024-04-03 10:53:13 UTC
Red Hat Product Errata RHSA-2024:2088 0 None None None 2024-04-29 02:26:54 UTC
Red Hat Product Errata RHSA-2024:2833 0 None None None 2024-05-14 09:08:18 UTC
Red Hat Product Errata RHSA-2024:3527 0 None None None 2024-05-30 20:25:39 UTC

Description TEJ RATHI 2024-01-29 11:01:27 UTC
There is a regression in Vert.x 4.4 branch that leads to a memory leak due to the use of Netty FastThreadLocal data structures.

As a consequence, when the Vert.x HTTP client connects to a different host, it does make the leak progress furthermore, there might be other cases leading to the same effect but exhibiting one seems enough to demonstrate the feasability.

Thus, this can be exploited with intimate knowledge of the runtime to accelerate the memory leak, e.g. a server accepting arbitrary internet addresses for which it will connect to could be fed with addresses as an attack vector.

This affects the maven artifact io.vertx:vertx-core versions 4.4.5, 4.4.6, 4.5.0, 4.5.1

https://github.com/eclipse-vertx/vert.x/issues/5078
https://github.com/eclipse-vertx/vert.x/pull/5082
https://github.com/eclipse-vertx/vert.x/pull/5080

Comment 7 errata-xmlrpc 2024-04-03 10:53:09 UTC
This issue has been addressed in the following products:

  Red Hat build of Quarkus 3.2.11

Via RHSA-2024:1662 https://access.redhat.com/errata/RHSA-2024:1662

Comment 8 errata-xmlrpc 2024-04-29 02:26:50 UTC
This issue has been addressed in the following products:

  Cryostat 2 on RHEL 8

Via RHSA-2024:2088 https://access.redhat.com/errata/RHSA-2024:2088

Comment 11 errata-xmlrpc 2024-05-14 09:08:13 UTC
This issue has been addressed in the following products:

  RHINT Service Registry 2.5.11 GA

Via RHSA-2024:2833 https://access.redhat.com/errata/RHSA-2024:2833

Comment 13 errata-xmlrpc 2024-05-30 20:25:34 UTC
This issue has been addressed in the following products:

  Red Hat AMQ Streams 2.7.0

Via RHSA-2024:3527 https://access.redhat.com/errata/RHSA-2024:3527


Note You need to log in before you can comment on or make changes to this bug.