CVE Vulnerabilities

CVE-2024-1300

Missing Release of Resource after Effective Lifetime

Published: Apr 02, 2024 | Modified: Feb 25, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
5.4 MODERATE
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L
Ubuntu
root.io logo minimus.io logo echo.ai logo

A vulnerability in the Eclipse Vert.x toolkit causes a memory leak in TCP servers configured with TLS and SNI support. When processing an unknown SNI server name assigned the default certificate instead of a mapped certificate, the SSL context is erroneously cached in the server name map, leading to memory exhaustion. This flaw allows attackers to send TLS client hello messages with fake server names, triggering a JVM out-of-memory error.

Weakness

The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.

Affected Software

NameVendorStart VersionEnd Version
CEQ 3.2RedHatvertx-core*
Cryostat 2 on RHEL 8RedHatcryostat-tech-preview/cryostat-grafana-dashboard-rhel8:2.4.0-7*
Cryostat 2 on RHEL 8RedHatcryostat-tech-preview/cryostat-operator-bundle:2.4.0-4*
Cryostat 2 on RHEL 8RedHatcryostat-tech-preview/cryostat-reports-rhel8:2.4.0-4*
Cryostat 2 on RHEL 8RedHatcryostat-tech-preview/cryostat-rhel8:2.4.0-4*
Cryostat 2 on RHEL 8RedHatcryostat-tech-preview/cryostat-rhel8-operator:2.4.0-9*
Cryostat 2 on RHEL 8RedHatcryostat-tech-preview/jfr-datasource-rhel8:2.4.0-4*
Migration Toolkit for Runtimes 1 on RHEL 8RedHatmtr/mtr-operator-bundle:1.2-18*
Migration Toolkit for Runtimes 1 on RHEL 8RedHatmtr/mtr-rhel8-operator:1.2-11*
Migration Toolkit for Runtimes 1 on RHEL 8RedHatmtr/mtr-web-container-rhel8:1.2-12*
Migration Toolkit for Runtimes 1 on RHEL 8RedHatmtr/mtr-web-executor-container-rhel8:1.2-10*
MTA-6.2-RHEL-9RedHatmta/mta-windup-addon-rhel9:6.2.3-2*
Red Hat AMQ Streams 2.7.0RedHatvertx-core*
Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2RedHatvertx-core*
Red Hat build of Quarkus 3.2.11.FinalRedHatio.vertx/vertx-core:4.4.8.redhat-00001*
RHINT Service Registry 2.5.11 GARedHatvertx-core*

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.
  • Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.
  • When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.
  • Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).

References