{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47065 exists.","fix":"No fix has been published for CVE-2024-47065 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-47065 is a low-severity denial of service vulnerability in meshtastic firmware, published on 11 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-47065 and fix it if it is affected.\n\nWhat it is: CVE-2024-47065 is a low-severity denial of service vulnerability in meshtastic firmware, published on 11 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-47065 exists.\n\nAffected product: meshtastic firmware. 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-47065/ (Markdown: https://insights.sbomify.com/CVE-2024-47065/index.md)","id":"CVE-2024-47065","markdown":"https://insights.sbomify.com/CVE-2024-47065/index.md","name":"CVE-2024-47065","record":{"aliases":[],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Meshtastic firmware","requires_auth":"none","summary":"Attackers can flood remote nodes with traceroute requests, causing network denial of service and rapidly extracting positional data.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"meshtastic_firmware","vendor":"meshtastic"}],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-799","name":"Improper Control of Interaction Frequency"}],"description":"Meshtastic is an open source mesh networking solution. Prior to 2.5.1, traceroute responses from the remote node are not rate limited. Given that there are SNR measurements attributed to each received transmission, this is a guaranteed way to get a remote station to reliably and continuously respond. You could easily get 100 samples in a short amount of time (estimated 2 minutes), whereas passively doing the same could take hours or days. There are secondary effects that non-ratelimited traceroute does also allow a 2:1 reflected DoS of the network as well, but these concerns are less than the problem with positional confidentiality (other DoS routes exist). This vulnerability is fixed in 2.5.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Traceroute_APP responses are not rate-limited.","id":"CVE-2024-47065","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Lobe Chat has insufficient fix for GHSA-mxhq-xw3g-rphc (CVE-2024-32964)","id":"CVE-2024-47066"},"packages":[],"prev":{"headline":"Computer Vision Annotation Tool (CVAT) contains a reflected XSS via request endpoints","id":"CVE-2024-47064"},"products":["firmware"],"published":"2025-07-11","related":[{"cvss_score":9.5,"headline":"Meshtastic Repeated Public and Private Keypairs","id":"CVE-2025-52464","kev_date_added":null,"published":"2025-06-19"},{"cvss_score":9.4,"headline":"Meshtastic allows crafting of specific NodeInfo packets that overwrite any publicKey saved in the NodeDB","id":"CVE-2025-55293","kev_date_added":null,"published":"2025-08-18"},{"cvss_score":9.4,"headline":"Meshtastic incorrectly hands malformed packets leads to controlled buffer overflow","id":"CVE-2025-24797","kev_date_added":null,"published":"2025-04-14"},{"cvss_score":8.2,"headline":"In Meshtastic, an attacker can spoof licensed amateur flag for a node","id":"CVE-2025-55292","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":8.1,"headline":"Meshtastic firmware Authentication/Authorization Bypass via MQTT","id":"CVE-2024-47078","kev_date_added":null,"published":"2024-09-25"},{"cvss_score":7.5,"headline":"Meshtastic: Malformed UTF-8 in User.long_name broadcast over LoRa causes mesh-wide client decode failure","id":"CVE-2026-42566","kev_date_added":null,"published":"2026-07-19"},{"cvss_score":7.5,"headline":"Device crash via malformed MQTT packet when downlink is enabled in Meshtastic device firmware","id":"CVE-2024-45038","kev_date_added":null,"published":"2024-08-27"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-11","vendors":["meshtastic"]},"summary":"Attackers can flood remote nodes with traceroute requests, causing network denial of service and rapidly extracting positional data.","url":"https://insights.sbomify.com/CVE-2024-47065/"}