Bootloader memory corruption via unchecked destination address
Published May 10, 2022 · Updated Sep 16, 2024
Improper input validation in 2nd and 3rd Gen AMD EPYC processors allows local users to overwrite bootloader memory with SPI ROM contents. The SVC_LOAD_FW_IMAGE_BY_INSTANCE and SVC_LOAD_BINARY_BY_ATTRIB services accept a destination address without adequate validation and copy SPI ROM contents into attacker-chosen bootloader memory. Exploitation requires a malicious or compromised UApp or ABL and can corrupt bootloader state or interrupt system availability.
Summary
What happened
Improper input validation in 2nd and 3rd Gen AMD EPYC processors allows local users to overwrite bootloader memory with SPI ROM contents. The SVC_LOAD_FW_IMAGE_BY_INSTANCE and SVC_LOAD_BINARY_BY_ATTRIB services accept a destination address without adequate validation and copy SPI ROM contents into attacker-chosen bootloader memory. Exploitation requires a malicious or compromised UApp or ABL and can corrupt bootloader state or interrupt system availability.
The record
- CVE
- CVE-2021-26370
- Published
- May 10, 2022
- Updated
- Sep 16, 2024
- Vendor
- Advanced Micro Devices, Inc.
- Product
- 3rd Gen AMD EPYC Processors
- Classifications
- CWE-20, T1495
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 10, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=unspecified <MilanPI-SP3_1.0.0.4
What conditions does exploitation require?
What is affected?
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