Integrity loss via out-of-range SPI reads
Published Nov 14, 2023 · Updated Aug 4, 2024
Improper address validation in AMD Ryzen ASP bootloader firmware allows physically proximate attackers to cause integrity loss or service interruption. The bootloader accepts SPI flash addresses beyond the flash boundary and reads adjacent memory-mapped regions instead of rejecting them. Physical access to an affected x86 platform is required; successful exploitation can compromise integrity or interrupt startup, with no reported confidentiality impact.
Summary
What happened
Improper address validation in AMD Ryzen ASP bootloader firmware allows physically proximate attackers to cause integrity loss or service interruption. The bootloader accepts SPI flash addresses beyond the flash boundary and reads adjacent memory-mapped regions instead of rejecting them. Physical access to an affected x86 platform is required; successful exploitation can compromise integrity or interrupt startup, with no reported confidentiality impact.
The record
- CVE
- CVE-2021-46758
- Published
- Nov 14, 2023
- Updated
- Aug 4, 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
- Nov 14, 2023CVE publishedPublication date reported by the CVE source.
- Aug 4, 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