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.
Workaround:
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHSA-2024:1662 | vendor advisory |
https://access.redhat.com/errata/RHSA-2024:1706 | vendor advisory |
https://access.redhat.com/errata/RHSA-2024:1923 | vendor advisory |
https://access.redhat.com/errata/RHSA-2024:2088 | vendor advisory |
https://access.redhat.com/errata/RHSA-2024:2833 | vendor advisory |
https://access.redhat.com/errata/RHSA-2024:3527 | vendor advisory |
https://access.redhat.com/errata/RHSA-2024:3989 | vendor advisory |
https://access.redhat.com/errata/RHSA-2024:4884 | vendor advisory |
https://access.redhat.com/security/cve/CVE-2024-1300 | vdb entry |
https://bugzilla.redhat.com/show_bug.cgi?id=2263139 | issue tracking |
https://vertx.io/docs/vertx-core/java/#_server_name_indication_sni. |