SPI ROM modification via chipset-option side effect
Published Nov 16, 2021 · Updated Sep 16, 2024
Protection mechanism failure in AMD 1st, 2nd, and 3rd Gen EPYC processors allows local users to modify SPI ROM contents. An integrated chipset option produces an undisclosed side effect that bypasses SPI ROM write protections instead of enforcing them. Low-privileged local access is sufficient, and successful exploitation permits unauthorized persistent firmware writes without reported data disclosure or service interruption.
Summary
What happened
Protection mechanism failure in AMD 1st, 2nd, and 3rd Gen EPYC processors allows local users to modify SPI ROM contents. An integrated chipset option produces an undisclosed side effect that bypasses SPI ROM write protections instead of enforcing them. Low-privileged local access is sufficient, and successful exploitation permits unauthorized persistent firmware writes without reported data disclosure or service interruption.
The record
- CVE
- CVE-2020-12954
- Published
- Nov 16, 2021
- Updated
- Sep 16, 2024
- Vendor
- AMD
- Product
- 2nd Gen AMD EPYC Processors
- Classifications
- CWE-693, T1542.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 16, 2021CVE 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 <RomePI-SP3_1.0.0.C
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