Privilege escalation via unvalidated ABL DRAM writes
Published Nov 14, 2023 · Updated Oct 11, 2024
Insufficient input validation in AMD processor ABL firmware allows attackers to write arbitrary DRAM and escalate privileges. ABL accepts a boot image without adequately validating attacker-controlled input before using it to issue DRAM writes. Exploitation requires privileged ability to write the boot image; successful use enables code execution and privilege escalation across the platform firmware trust boundary.
Summary
What happened
Insufficient input validation in AMD processor ABL firmware allows attackers to write arbitrary DRAM and escalate privileges. ABL accepts a boot image without adequately validating attacker-controlled input before using it to issue DRAM writes. Exploitation requires privileged ability to write the boot image; successful use enables code execution and privilege escalation across the platform firmware trust boundary.
The record
- CVE
- CVE-2021-46774
- Published
- Nov 14, 2023
- Updated
- Oct 11, 2024
- Vendor
- AMD
- Product
- 4th Gen AMD EPYC Processors
- Classifications
- T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 14, 2023CVE publishedPublication date reported by the CVE source.
- Oct 11, 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