{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40427 exists.","fix":"No fix has been published for CVE-2024-40427 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-40427 is a high-severity memory corruption vulnerability in n/a, published on 7 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-40427 and fix it if it is affected.\n\nWhat it is: CVE-2024-40427 is a high-severity memory corruption vulnerability in n/a, published on 7 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40427 exists.\n\nAffected product: n/a. 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-40427/ (Markdown: https://insights.sbomify.com/CVE-2024-40427/index.md)","id":"CVE-2024-40427","markdown":"https://insights.sbomify.com/CVE-2024-40427/index.md","name":"CVE-2024-40427","record":{"aliases":["GHSA-55wq-2hgm-75m4","GHSA-w3wc-83g3-v333"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PX4 Autopilot","requires_auth":"low_privilege","summary":"Attackers can exploit a stack buffer overflow in PX4 Autopilot to execute arbitrary commands or cause a denial of service.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"px4_drone_autopilot","vendor":"dronecode"}],"cvss":{"score":7.9,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"Stack Buffer Overflow in PX4-Autopilot v1.14.3, which allows attackers to execute commands to exploit this vulnerability and cause the program to refuse to execute","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":"Memory corruption in n/a","id":"CVE-2024-40427","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2024-40430"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2024-40425"},"products":["n/a"],"published":"2025-01-07","related":[{"cvss_score":8.1,"headline":"Business logic in n/a","id":"CVE-2026-26741","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":8.1,"headline":"Security feature bypass in n/a","id":"CVE-2026-26742","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":7.8,"headline":"Zenoh uORB Subscriber Allows Arbitrary Stack Allocation (PX4/PX4-Autopilot)","id":"CVE-2026-32708","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2024-38952","kev_date_added":null,"published":"2024-06-25"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2021-46896","kev_date_added":null,"published":"2023-07-06"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2021-34125","kev_date_added":null,"published":"2023-03-09"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-08","vendors":["n/a"]},"summary":"Attackers can exploit a stack buffer overflow in PX4 Autopilot to execute arbitrary commands or cause a denial of service.","url":"https://insights.sbomify.com/CVE-2024-40427/"}