{"answers":{"affected":"4 open source packages ship an affected version, including io.vertx:vertx-core.","exploited":"There is no known exploitation of CVE-2024-1300 in the wild and no public exploit code.","fix":"Upgrade io.vertx:vertx-core to a fixed version for your release line: 4.4.8 or 4.5.3.","what":"CVE-2024-1300 is a medium-severity denial of service vulnerability in Red Hat A-MQ Clients 2, published on 2 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-1300 and fix it if it is affected.\n\nWhat it is: CVE-2024-1300 is a medium-severity denial of service vulnerability in Red Hat A-MQ Clients 2, published on 2 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-1300 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.vertx:vertx-core (Maven): affected from 4.3.4; fixed in 4.4.8\n- io.vertx:vertx-core (Maven): affected from 4.3.4; fixed in 4.4.8\n- io.vertx:vertx-core (Maven): affected from 4.5.0; fixed in 4.5.3\n- io.vertx:vertx-core (Maven): affected from 4.5.0; fixed in 4.5.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-1300/ (Markdown: https://insights.sbomify.com/CVE-2024-1300/index.md)","id":"CVE-2024-1300","markdown":"https://insights.sbomify.com/CVE-2024-1300/index.md","name":"CVE-2024-1300","record":{"aliases":["GHSA-9ph3-v2vh-3qx7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Java networking library","requires_auth":"low_privilege","summary":"Attackers can cause a denial of service by exhausting memory in Vert.x TCP servers using TLS and SNI with unknown server names.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-772","name":"Missing Release of Resource after Effective Lifetime"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Io.vertx:vertx-core: memory leak when a tcp server is configured with tls and sni support","id":"CVE-2024-1300","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":4,"n_references":11,"next":{"headline":"Multiple Vulnerabilities in Badger Meter's Monitool","id":"CVE-2024-1301"},"packages":[{"ecosystem":"Maven","fixed":["4.4.8"],"introduced":["4.3.4"],"last_affected":[],"package":"io.vertx:vertx-core","purl":null,"source":"GHSA-9ph3-v2vh-3qx7"},{"ecosystem":"Maven","fixed":["4.4.8"],"introduced":["4.3.4"],"last_affected":[],"package":"io.vertx:vertx-core","purl":"pkg:maven/io.vertx/vertx-core","source":"GHSA-9ph3-v2vh-3qx7"},{"ecosystem":"Maven","fixed":["4.5.3"],"introduced":["4.5.0"],"last_affected":[],"package":"io.vertx:vertx-core","purl":null,"source":"GHSA-9ph3-v2vh-3qx7"},{"ecosystem":"Maven","fixed":["4.5.3"],"introduced":["4.5.0"],"last_affected":[],"package":"io.vertx:vertx-core","purl":"pkg:maven/io.vertx/vertx-core","source":"GHSA-9ph3-v2vh-3qx7"}],"prev":{"headline":"Privilege Chaining in GitLab","id":"CVE-2024-1299"},"products":["A-MQ Clients 2","CEQ 3.2","Cryostat 2 on RHEL 8","MTA-6.2-RHEL-9","Migration Toolkit for Runtimes 1 on RHEL 8","OpenShift Serverless","RHINT Service Registry 2.5.11 GA","Red Hat AMQ Broker 7","Red Hat AMQ Streams 2.7.0","Red Hat Build of Keycloak","Red Hat Data Grid 8","Red Hat Fuse 7","Red Hat Integration Camel K 1","Red Hat Integration Camel Quarkus 2","Red Hat JBoss Data Grid 7","Red Hat JBoss Enterprise Application Platform 7","Red Hat JBoss Enterprise Application Platform 8","Red Hat JBoss Enterprise Application Platform Expansion Pack","Red Hat Process Automation 7","Red Hat build of Apache Camel 4 for Quarkus 3","Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2","Red Hat build of Apache Camel for Spring Boot 3","Red Hat build of OptaPlanner 8","Red Hat build of Quarkus","Red Hat build of Quarkus 3.2.11.Final"],"published":"2024-04-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-23","vendors":["Red Hat"]},"summary":"Attackers can cause a denial of service by exhausting memory in Vert.x TCP servers using TLS and SNI with unknown server names.","url":"https://insights.sbomify.com/CVE-2024-1300/"}