{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-23907 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-23907 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-23907 is a low-severity vulnerability in n/a, published on 13 May 2021. 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-2021-23907 and fix it if it is affected.\n\nWhat it is: CVE-2021-23907 is a low-severity vulnerability in n/a, published on 13 May 2021. 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: There is no known exploitation of CVE-2021-23907 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-2021-23907/ (Markdown: https://insights.sbomify.com/CVE-2021-23907/index.md)","id":"CVE-2021-23907","markdown":"https://insights.sbomify.com/CVE-2021-23907/index.md","name":"CVE-2021-23907","record":{"aliases":["GHSA-h34f-cf95-vh44"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Mercedes-Benz Infotainment","requires_auth":"none","summary":"Attackers can achieve remote code execution on Mercedes-Benz MBUX infotainment systems due to unchecked count values in the HiQnet Protocol.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"headunit_ntg6_mercedes-benz_user_experience","vendor":"mercedes-benz"}],"cvss":{"score":2.9,"severity":"low","source":"cna","vector":"CVSS:3.1/AC:H/AV:P/A:N/C:L/I:L/PR:N/S:U/UI:R","version":"3.1"},"cwes":[],"description":"An issue was discovered in the Headunit NTG6 in the MBUX Infotainment System on Mercedes-Benz vehicles through 2021. The count in MultiSvGet, GetAttributes, and MultiSvSet is not checked in the HiQnet Protocol, leading to remote code execution.","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":"Integer overflow in n/a","id":"CVE-2021-23907","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2021-23908"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2021-23906"},"products":["n/a"],"published":"2021-05-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can achieve remote code execution on Mercedes-Benz MBUX infotainment systems due to unchecked count values in the HiQnet Protocol.","url":"https://insights.sbomify.com/CVE-2021-23907/"}