Memory corruption via malformed SPI ROM headers
Published Aug 13, 2024 · Updated Nov 5, 2024
Out-of-bounds read and write in AMD ABL firmware across affected processors allows privileged local users to corrupt memory via SPI ROM changes. ABL inadequately validates SPI ROM structure headers before using their values for memory access, permitting out-of-bounds reads and writes. Exploitation requires privileged access to the BIOS menu or UEFI shell; tampering can corrupt memory or interrupt service.
Summary
What happened
Out-of-bounds read and write in AMD ABL firmware across affected processors allows privileged local users to corrupt memory via SPI ROM changes. ABL inadequately validates SPI ROM structure headers before using their values for memory access, permitting out-of-bounds reads and writes. Exploitation requires privileged access to the BIOS menu or UEFI shell; tampering can corrupt memory or interrupt service.
The record
- CVE
- CVE-2021-46772
- Published
- Aug 13, 2024
- Updated
- Nov 5, 2024
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Ryzen™ Embedded V1000 Series Processors
- Classifications
- CWE-787, CWE-125, T1495
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 13, 2024CVE publishedPublication date reported by the CVE source.
- Nov 5, 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
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