Local privilege escalation via unsigned MCU firmware
Published Nov 22, 2024 · Updated Nov 25, 2024
Insufficient firmware validation in Visteon Infotainment cmu150_NA_74.00.324A allows local users to execute arbitrary VIP MCU code. The vcm --write-image path programs a Motorola S-record into VIP internal memory without authenticating the image, accepting attacker-modified firmware. Low-privileged code execution on the Linux application SoC is required; exploitation crosses the SoC-MCU boundary and grants direct access to connected vehicle CAN buses.
Summary
What happened
Insufficient firmware validation in Visteon Infotainment cmu150_NA_74.00.324A allows local users to execute arbitrary VIP MCU code. The vcm --write-image path programs a Motorola S-record into VIP internal memory without authenticating the image, accepting attacker-modified firmware. Low-privileged code execution on the Linux application SoC is required; exploitation crosses the SoC-MCU boundary and grants direct access to connected vehicle CAN buses.
The record
- CVE
- CVE-2024-8356
- Published
- Nov 22, 2024
- Updated
- Nov 25, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-345, T1542.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 22, 2024CVE publishedPublication date reported by the CVE source.
- Nov 25, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo