Kernel code execution via bcmdhd buffer overrun
Published May 3, 2024 · Updated Sep 18, 2024
Out-of-bounds write in the bcmdhd driver in Tesla Model 3 software 2023.6 allows local users to execute code in the kernel. The driver fails to validate user-supplied data before writing it, allowing the write to pass the end of an allocated buffer. Exploitation requires prior code execution on the Wi-Fi subsystem and grants arbitrary code execution in the kernel context.
Summary
What happened
Out-of-bounds write in the bcmdhd driver in Tesla Model 3 software 2023.6 allows local users to execute code in the kernel. The driver fails to validate user-supplied data before writing it, allowing the write to pass the end of an allocated buffer. Exploitation requires prior code execution on the Wi-Fi subsystem and grants arbitrary code execution in the kernel context.
The record
- CVE
- CVE-2023-32155
- Published
- May 3, 2024
- Updated
- Sep 18, 2024
- Vendor
- Tesla
- Product
- Model 3
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
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=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.
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