{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-34401 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-34401 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-34401 is a low-severity memory corruption vulnerability in n/a, published on 13 Feb 2025. 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-34401 and fix it if it is affected.\n\nWhat it is: CVE-2023-34401 is a low-severity memory corruption vulnerability in n/a, published on 13 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-34401 in the wild and no public exploit code.\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-2023-34401/ (Markdown: https://insights.sbomify.com/CVE-2023-34401/index.md)","id":"CVE-2023-34401","markdown":"https://insights.sbomify.com/CVE-2023-34401/index.md","name":"CVE-2023-34401","record":{"aliases":["GHSA-gh3v-mv9p-hffw"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Mercedes-Benz head-unit","requires_auth":"low_privilege","summary":"An attacker with USB access can trigger an out-of-bounds read in the NTG6 head-unit, potentially exposing sensitive heap memory data.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"headunit_ntg6_mercedes-benz_user_experience","vendor":"mercedes-benz"}],"cvss":{"score":3.7,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Mercedes-Benz head-unit NTG6 contains functions to import or export profile settings over USB. Inside profile folder there is a file, which is encoded with proprietary UD2 codec. Due to missed size checks in the enapsulate file, attacker can achieve Out-of-Bound Read in heap memory.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2023-34401","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2023-34402"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2023-34400"},"products":["n/a"],"published":"2025-02-13","related":[{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2023-34399","kev_date_added":null,"published":"2025-02-13"},{"cvss_score":7.7,"headline":"Path traversal in n/a","id":"CVE-2023-34402","kev_date_added":null,"published":"2025-02-13"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2023-34397","kev_date_added":null,"published":"2025-02-13"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2023-34398","kev_date_added":null,"published":"2025-02-13"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2023-34400","kev_date_added":null,"published":"2025-02-13"},{"cvss_score":6.8,"headline":"Memory corruption in n/a","id":"CVE-2024-37600","kev_date_added":null,"published":"2025-02-13"},{"cvss_score":4.9,"headline":"Path traversal in n/a","id":"CVE-2023-34403","kev_date_added":null,"published":"2025-02-13"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-18","vendors":["n/a"]},"summary":"An attacker with USB access can trigger an out-of-bounds read in the NTG6 head-unit, potentially exposing sensitive heap memory data.","url":"https://insights.sbomify.com/CVE-2023-34401/"}