Skip to main content
VulnerabilityPublished Updated

CVE-2024-1023: Red Hat Cryostat 2 on RHEL 8 · Memory Leak

Affects Red Hat Cryostat 2 on RHEL 8Source CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.6% chance of exploitation in 30 days – higher than 76% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Mar 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatCEQ 3.2Affected–Fixed in–
Red HatCryostat 2 on RHEL 8Affected–Fixed in–
Red HatCryostat 2 on RHEL 8Affected–Fixed in–
Red HatCryostat 2 on RHEL 8Affected–Fixed in–
Red HatMTA-6.2-RHEL-9Affected–Fixed in–
Red HatRed Hat AMQ Streams 2.7.0Affected–Fixed in–

AI-suggested

Red Hat has released security updates for their build of Quarkus (version 3.2.11) and related products that address CVE-2024-1023. Users should apply these official patches as soon as possible. Before applying updates, it is recommended to back up existing installations, including applications, configuration files, and databases. No alternative mitigations or workarounds are indicated in the vendor advisories. Patch status is confirmed as fixed in the updated Red Hat packages.

Description

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.

References

Community reviews

Loading reviews…