Gateway code execution via stale update validation
Published May 3, 2024 · Updated Sep 18, 2024
Signature-validation bypass in Tesla Model 3 firmware before 2023.12 allows attackers to execute code on the Gateway ECU. The Gateway update mode leaves a valid update scheduled when an invalid second fetch overwrites its file, then applies that file without rechecking its signature. Exploitation requires privileged code execution on the infotainment system and permits arbitrary firmware to run in the security Gateway context.
Summary
What happened
Signature-validation bypass in Tesla Model 3 firmware before 2023.12 allows attackers to execute code on the Gateway ECU. The Gateway update mode leaves a valid update scheduled when an invalid second fetch overwrites its file, then applies that file without rechecking its signature. Exploitation requires privileged code execution on the infotainment system and permits arbitrary firmware to run in the security Gateway context.
The record
- CVE
- CVE-2023-32156
- Published
- May 3, 2024
- Updated
- Sep 18, 2024
- Vendor
- Tesla
- Product
- Model 3
- Classifications
- CWE-367, T1542.001
- Attack vector
- adjacent
- Privileges
- admin
Timeline
How it unfolded
- May 3, 2024CVE publishedPublication date reported by the CVE source.
- Sep 18, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=- <2023.12
- Affected versionversion=Model 3 - 2023.6
What conditions does exploitation require?
What is affected?
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