{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-24797 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-24797 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-24797 is a critical memory corruption vulnerability in meshtastic firmware, published on 14 Apr 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-2025-24797 and fix it if it is affected.\n\nWhat it is: CVE-2025-24797 is a critical memory corruption vulnerability in meshtastic firmware, published on 14 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-24797 in the wild and no public exploit code.\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-2025-24797/ (Markdown: https://insights.sbomify.com/CVE-2025-24797/index.md)","id":"CVE-2025-24797","markdown":"https://insights.sbomify.com/CVE-2025-24797/index.md","name":"CVE-2025-24797","record":{"aliases":["GHSA-33hw-xhfh-944r"],"analysis":{"component_type":"hardware_firmware","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Meshtastic firmware","requires_auth":"none","summary":"An attacker can achieve remote code execution on Meshtastic devices by sending malformed mesh packets that trigger a buffer overflow.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"meshtastic_firmware","vendor":"meshtastic"}],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Meshtastic is an open source mesh networking solution. A fault in the handling of mesh packets containing invalid protobuf data can result in an attacker-controlled buffer overflow, allowing an attacker to hijack execution flow, potentially resulting in remote code execution. This attack does not require authentication or user interaction, as long as the target device rebroadcasts packets on the default channel. This vulnerability fixed in 2.6.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-04-16","github_poc":1,"max_poc_stars":3,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-04-16T19:04:44Z","kind":"github_poc","ref":"https://github.com/Alainx277/CVE-2025-24797","stars":3,"title":"Meshtastic buffer overflow vulnerability - CVE-2025-24797"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Meshtastic incorrectly hands malformed packets leads to controlled buffer overflow","id":"CVE-2025-24797","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Meshtastic crashes via an unimplemented routing module reply","id":"CVE-2025-24798"},"packages":[],"prev":{"headline":"Remote Code Execution within Collabora Online jail with Macros Enabled","id":"CVE-2025-24796"},"products":["firmware"],"published":"2025-04-14","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":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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-21","vendors":["meshtastic"]},"summary":"An attacker can achieve remote code execution on Meshtastic devices by sending malformed mesh packets that trigger a buffer overflow.","url":"https://insights.sbomify.com/CVE-2025-24797/"}