{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-45038 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-45038 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-45038 is a high-severity denial of service vulnerability in meshtastic firmware, published on 27 Aug 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-45038 and fix it if it is affected.\n\nWhat it is: CVE-2024-45038 is a high-severity denial of service vulnerability in meshtastic firmware, published on 27 Aug 2024. 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-2024-45038 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-2024-45038/ (Markdown: https://insights.sbomify.com/CVE-2024-45038/index.md)","id":"CVE-2024-45038","markdown":"https://insights.sbomify.com/CVE-2024-45038/index.md","name":"CVE-2024-45038","record":{"aliases":["GHSA-3x3r-vw9f-pxq5"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Meshtastic device firmware","requires_auth":"none","summary":"Attackers can crash Meshtastic devices by sending malformed MQTT packets when downlink is enabled, requiring a firmware update.","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":7.5,"severity":"high","source":"cna","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-755","name":"Improper Handling of Exceptional Conditions"}],"description":"Meshtastic device firmware is a firmware for meshtastic devices to run an open source, off-grid, decentralized, mesh network built to run on affordable, low-power devices. Meshtastic device firmware is subject to a denial of serivce vulnerability in MQTT handling, fixed in version 2.4.1 of the Meshtastic firmware and on the Meshtastic public MQTT Broker. It's strongly suggested that all users of Meshtastic, particularly those that connect to a privately hosted MQTT server, update to this or a more recent stable version right away. 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":"none_known"},"has_fix":false,"headline":"Device crash via malformed MQTT packet when downlink is enabled in Meshtastic device firmware","id":"CVE-2024-45038","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":"gnark's Groth16 commitment extension unsound for more than one commitment","id":"CVE-2024-45039"},"packages":[],"prev":{"headline":"AWS CDK RestApi not generating authorizationScope correctly in resultant CFN template","id":"CVE-2024-45037"},"products":["firmware"],"published":"2024-08-27","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"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-28","vendors":["meshtastic"]},"summary":"Attackers can crash Meshtastic devices by sending malformed MQTT packets when downlink is enabled, requiring a firmware update.","url":"https://insights.sbomify.com/CVE-2024-45038/"}