{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-46256 exists.","fix":"No fix has been published for CVE-2023-46256 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46256 is a medium-severity memory corruption vulnerability in PX4-Autopilot, published on 31 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-46256 and fix it if it is affected.\n\nWhat it is: CVE-2023-46256 is a medium-severity memory corruption vulnerability in PX4-Autopilot, published on 31 Oct 2023. Any signed-in user can exploit it over the 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-2023-46256 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-2023-46256/ (Markdown: https://insights.sbomify.com/CVE-2023-46256/index.md)","id":"CVE-2023-46256","markdown":"https://insights.sbomify.com/CVE-2023-46256/index.md","name":"CVE-2023-46256","record":{"aliases":["GHSA-5hvv-q2r5-rppw"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Drone flight controller","requires_auth":"low_privilege","summary":"A heap buffer overflow in PX4-Autopilot allows malicious applications to write arbitrary data to memory, potentially causing unexpected drone behavior or code execution.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"px4_drone_autopilot","vendor":"dronecode"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"},{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"PX4-Autopilot provides PX4 flight control solution for drones. In versions 1.14.0-rc1 and prior, PX4-Autopilot has a heap buffer overflow vulnerability in the parser function due to the absence of `parserbuf_index` value checking. A malfunction of the sensor device can cause a heap buffer overflow with leading unexpected drone behavior. Malicious applications can exploit the vulnerability even if device sensor malfunction does not occur. Up to the maximum value of an `unsigned int`, bytes sized data can be written to the heap memory area. As of time of publication, no fixed version is available.","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":"PX4-Autopilot Heap Buffer Overflow Bug","id":"CVE-2023-46256","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Avalanche","id":"CVE-2023-46257"},"packages":[],"prev":{"headline":"`SPICEDB_DATASTORE_CONN_URI` is leaked when URI cannot be parsed","id":"CVE-2023-46255"},"products":["PX4-Autopilot"],"published":"2023-10-31","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.9,"headline":"Memory corruption in n/a","id":"CVE-2024-40427","kev_date_added":null,"published":"2025-01-07"},{"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":"2024-09-05","vendors":["PX4"]},"summary":"A heap buffer overflow in PX4-Autopilot allows malicious applications to write arbitrary data to memory, potentially causing unexpected drone behavior or code execution.","url":"https://insights.sbomify.com/CVE-2023-46256/"}