{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51500 exists.","fix":"No fix has been published for CVE-2024-51500 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-51500 is a medium-severity denial of service vulnerability in meshtastic firmware, published on 4 Nov 2024. 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-51500 and fix it if it is affected.\n\nWhat it is: CVE-2024-51500 is a medium-severity denial of service vulnerability in meshtastic firmware, published on 4 Nov 2024. 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-51500 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-51500/ (Markdown: https://insights.sbomify.com/CVE-2024-51500/index.md)","id":"CVE-2024-51500","markdown":"https://insights.sbomify.com/CVE-2024-51500/index.md","name":"CVE-2024-51500","record":{"aliases":["GHSA-xfmq-5j3j-vgv8"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Meshtastic firmware","requires_auth":"none","summary":"Attackers can spoof broadcast addresses to amplify messages, causing network-wide bandwidth exhaustion and degraded performance in Meshtastic devices.","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":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-159","name":"Improper Handling of Invalid Use of Special Elements"},{"id":"CWE-138","name":"Improper Neutralization of Special Elements"}],"description":"Meshtastic firmware is a device firmware for the Meshtastic project. The Meshtastic firmware does not check for packets claiming to be from the special broadcast address (0xFFFFFFFF) which could result in unexpected behavior and potential for DDoS attacks on the network. A malicious actor could craft a packet to be from that address which would result in an amplification of this one message into every node on the network sending multiple messages. Such an attack could result in degraded network performance for all users as the available bandwidth is consumed. This issue has been addressed in release version 2.5.6. All users are advised to upgrade. There are no known workarounds for this vulnerability.","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":"Denial of service in firmware","id":"CVE-2024-51500","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":"CRLF injection in Refit's [Header], [HeaderCollection] and [Authorize] attributes","id":"CVE-2024-51501"},"packages":[],"prev":{"headline":"MarkUs Arbitrary File Write leading up to remote code execution (student accounts)","id":"CVE-2024-51499"},"products":["firmware"],"published":"2024-11-04","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":"2024-11-05","vendors":["meshtastic"]},"summary":"Attackers can spoof broadcast addresses to amplify messages, causing network-wide bandwidth exhaustion and degraded performance in Meshtastic devices.","url":"https://insights.sbomify.com/CVE-2024-51500/"}