{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-42651 exists.","fix":"No fix has been published for CVE-2024-42651 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-42651 is a high-severity use after free vulnerability in n/a, published on 29 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-42651 and fix it if it is affected.\n\nWhat it is: CVE-2024-42651 is a high-severity use after free vulnerability in n/a, published on 29 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-42651 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-42651/ (Markdown: https://insights.sbomify.com/CVE-2024-42651/index.md)","id":"CVE-2024-42651","markdown":"https://insights.sbomify.com/CVE-2024-42651/index.md","name":"CVE-2024-42651","record":{"aliases":["GHSA-fx4f-94f8-r3jm"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MQTT broker","requires_auth":"none","summary":"Attackers can cause a Denial of Service in NanoMQ by sending a crafted SUBSCRIBE message that triggers a heap use-after-free.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nanomq","vendor":"emqx"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"NanoMQ v0.17.9 was discovered to contain a heap use-after-free vulnerability via the component sub_Ctx_handle. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted SUBSCRIBE message.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Use after free in n/a","id":"CVE-2024-42651","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2024-42655"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2024-42650"},"products":["n/a"],"published":"2025-07-29","related":[{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2024-42655","kev_date_added":null,"published":"2025-07-29"},{"cvss_score":8.5,"headline":"NanoMQ has Buffer Overflow","id":"CVE-2025-59947","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":8,"headline":"Memory corruption in n/a","id":"CVE-2023-34488","kev_date_added":null,"published":"2023-06-12"},{"cvss_score":7.7,"headline":"NanoMQ has Heap Buffer Overflow in URI Parameter Parsing","id":"CVE-2026-32135","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2026-36590","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":7.5,"headline":"MQTT v5 Variable Byte Integer parsing out-of-bounds: get_var_integer()","id":"CVE-2026-21888","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-48077","kev_date_added":null,"published":"2026-01-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-29","vendors":["n/a"]},"summary":"Attackers can cause a Denial of Service in NanoMQ by sending a crafted SUBSCRIBE message that triggers a heap use-after-free.","url":"https://insights.sbomify.com/CVE-2024-42651/"}