Skip to content
VulniPulse
Medium5.4Red Hat Linux

Medium [CVE-2024-1300] Io.vertx:vertx-core: memory leak when a tcp server is configured with tls and sni support

This medium-severity Red Hat Linux advisory covers CVE-2024-1300 affecting Cryostat 2 on RHEL 8, Migration Toolkit for Runtimes 1 on RHEL 8, MTA-6.2-RHEL-9.

CVE-2024-1300 Published Apr 2, 2024Updated by vendor Aug 4, 2026
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

Affected products named by the advisory: Cryostat 2 on RHEL 8; Migration Toolkit for Runtimes 1 on RHEL 8; MTA-6.2-RHEL-9; Red Hat build of Quarkus 3.2.11.Final; and 8 more.

Affected products named by the advisory: Red Hat build of Apache Camel for Spring Boot 3; Red Hat Build of Keycloak; Red Hat build of OptaPlanner 8; Red Hat Integration Camel K 1; and 3 more.

Affected products named by the advisory: Red Hat Integration Camel Quarkus 2; Red Hat JBoss Data Grid 7; Red Hat Process Automation 7.

Affected versions
  • 4.3.4 through 4.5.2

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.