{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5640 exists.","fix":"No fix has been published for CVE-2025-5640 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-5640 is a medium-severity memory corruption vulnerability in PX4-Autopilot, published on 5 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-5640 and fix it if it is affected.\n\nWhat it is: CVE-2025-5640 is a medium-severity memory corruption vulnerability in PX4-Autopilot, published on 5 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5640 exists.\n\nAffected product: PX4-Autopilot. 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-5640/ (Markdown: https://insights.sbomify.com/CVE-2025-5640/index.md)","id":"CVE-2025-5640","markdown":"https://insights.sbomify.com/CVE-2025-5640/index.md","name":"CVE-2025-5640","record":{"aliases":["GHSA-rggh-j84q-m7ww"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PX4 Autopilot","requires_auth":"low_privilege","summary":"A stack-based buffer overflow in PX4-Autopilot allows local attackers to execute arbitrary code or cause denial of service via crafted MAVLink messages.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A vulnerability was found in PX4-Autopilot 1.12.3. It has been classified as problematic. This affects the function MavlinkReceiver::handle_message_trajectory_representation_waypoints of the file mavlink_receiver.cpp of the component TRAJECTORY_REPRESENTATION_WAYPOINTS Message Handler. The manipulation leads to stack-based buffer overflow. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2025-06-21","github_poc":1,"max_poc_stars":3,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-06-21T11:52:01Z","kind":"github_poc","ref":"https://github.com/mbanyamer/PX4-Military-UAV-Autopilot-1.12.3-Stack-Buffer-Overflow-Exploit-CVE-2025-5640-","stars":3,"title":null},{"date":"2025-06-26","kind":"exploitdb","ref":"52339","stars":null,"title":"PX4 Military UAV Autopilot 1.12.3 - Denial of Service (DoS)"}],"tier":"weaponised"},"has_fix":false,"headline":"PX4-Autopilot TRAJECTORY_REPRESENTATION_WAYPOINTS Message mavlink_receiver.cpp stack-based overflow","id":"CVE-2025-5640","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"Radare2 radiff2 cons.c r_cons_is_breaked memory corruption","id":"CVE-2025-5641"},"packages":[],"prev":{"headline":"PHPGurukul Notice Board System forgot-password.php sql injection","id":"CVE-2025-5639"},"products":["PX4-Autopilot"],"published":"2025-06-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-05","vendors":["n/a"]},"summary":"A stack-based buffer overflow in PX4-Autopilot allows local attackers to execute arbitrary code or cause denial of service via crafted MAVLink messages.","url":"https://insights.sbomify.com/CVE-2025-5640/"}