Physical code execution via voltage fault injection
Published Aug 8, 2023 · Updated Nov 13, 2024
Voltage fault injection in AMD Ryzen and Athlon processors allows physically proximate attackers to compromise ASP secure boot and execute code. Externally induced voltage faults during fTPM-related ASP secure boot defeat that trust boundary; AMD has not published further electrical timing details. Exploitation requires specialized hardware and prolonged physical access to an individual unit, with resulting code execution in the secure-boot context.
Summary
What happened
Voltage fault injection in AMD Ryzen and Athlon processors allows physically proximate attackers to compromise ASP secure boot and execute code. Externally induced voltage faults during fTPM-related ASP secure boot defeat that trust boundary; AMD has not published further electrical timing details. Exploitation requires specialized hardware and prolonged physical access to an individual unit, with resulting code execution in the secure-boot context.
The record
- CVE
- CVE-2023-20589
- Published
- Aug 8, 2023
- Updated
- Nov 13, 2024
- Vendor
- AMD
- Product
- AMD Ryzen 7035 Series Processors with Radeon Graphics (Rembrandt-R)
- Classifications
- Unavailable
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 2023CVE publishedPublication date reported by the CVE source.
- Nov 13, 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=various
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
No sourced classifications are available.
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