CVE-2024-8357
Visteon Infotainment cmu150_na_74.00.324a
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-8357 is a high-severity Missing Immutable Root of Trust in Hardware (CWE-1326) vulnerability in Visteon Infotainment. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Pre-OS Boot (T1542); ranked at the 25th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-34 (Non-modifiable Executable Programs) and SC-51 (Hardware-based Protection) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-49540
Vulnerability Data
Visteon Infotainment App SoC Missing Immutable Root of Trust in Hardware Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Visteon Infotainment systems. Although authentication is required to exploit this vulnerability, the existing…
more
authentication mechanism can be bypassed. The specific flaw exists within the configuration of the application system-on-chip (SoC). The issue results from the lack of properly configured hardware root of trust. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of the boot process. Was ZDI-CAN-23759.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Requires hardware-enforced loading and execution of the operating environment from a protected source, directly establishing an immutable hardware root of trust.
Mandates hardware-based write-protect mechanisms that can implement and protect an immutable root of trust against tampering.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Assessing hardware authenticity/integrity before acquisition directly prevents purchase of devices lacking an immutable root of trust.
Replacing hardware that lacks required security capabilities (e.g., immutable root of trust) mitigates the weakness over the asset lifecycle.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure system architecture and engineering principles require hardware roots of trust to prevent bypass of secure boot.
Cryptographic controls can protect the root of trust but do not mandate its hardware immutability.
Change management can protect firmware updates but does not ensure an immutable hardware root of trust exists.
Configuration management can enforce secure boot settings but does not address the absence of an immutable hardware root.