{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2018-18203 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18203 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18203 is a medium-severity code injection vulnerability in n/a, published on 28 Nov 2018. 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-2018-18203 and fix it if it is affected.\n\nWhat it is: CVE-2018-18203 is a medium-severity code injection vulnerability in n/a, published on 28 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-18203 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-2018-18203/ (Markdown: https://insights.sbomify.com/CVE-2018-18203/index.md)","id":"CVE-2018-18203","markdown":"https://insights.sbomify.com/CVE-2018-18203/index.md","name":"CVE-2018-18203","record":{"aliases":["GHSA-77mp-2cr5-w6pc"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Subaru StarLink head unit","requires_auth":"none","summary":"An attacker with physical USB access can inject malicious firmware into Subaru StarLink head units, achieving root-level arbitrary code execution.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"starlink_2017_firmware","vendor":"subaru"},{"product":"starlink_2018_firmware","vendor":"subaru"},{"product":"starlink_2019_firmware","vendor":"subaru"}],"cvss":{"score":6.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"A vulnerability in the update mechanism of Subaru StarLink Harman head units 2017, 2018, and 2019 may give an attacker (with physical access to the vehicle's USB ports) the ability to rewrite the firmware of the head unit. This occurs because the device accepts modified QNX6 filesystem images (as long as the attacker obtains access to certain Harman decryption/encryption code) as a consequence of a bug where unsigned images pass a validity check. An attacker could potentially install persistent malicious head unit firmware and execute arbitrary code as the root user.","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":"Code injection in n/a","id":"CVE-2018-18203","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-18205"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2018-18202"},"products":["n/a"],"published":"2018-11-28","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker with physical USB access can inject malicious firmware into Subaru StarLink head units, achieving root-level arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2018-18203/"}