Physical code execution via ABL memory overwrite
Published May 9, 2023 · Updated Jan 28, 2025
Improper input validation in AMD EPYC AGESA ABL allows physically proximate attackers to overwrite memory and execute code. AMD identifies only the AGESA Boot Loader locus; it does not disclose which input is accepted without validation or how that input selects arbitrary memory destinations. Physical access to an affected 2nd or 3rd Gen EPYC server is required, and successful exploitation compromises platform memory integrity and permits code execution.
Summary
What happened
Improper input validation in AMD EPYC AGESA ABL allows physically proximate attackers to overwrite memory and execute code. AMD identifies only the AGESA Boot Loader locus; it does not disclose which input is accepted without validation or how that input selects arbitrary memory destinations. Physical access to an affected 2nd or 3rd Gen EPYC server is required, and successful exploitation compromises platform memory integrity and permits code execution.
The record
- CVE
- CVE-2021-46775
- Published
- May 9, 2023
- Updated
- Jan 28, 2025
- Vendor
- Advanced Micro Devices, Inc.
- Product
- 3rd Gen AMD EPYC Processors
- Classifications
- CWE-20
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2023CVE publishedPublication date reported by the CVE source.
- Jan 28, 2025Record 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?
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