Platform-key disclosure via fixed AES-CTR initialization vector
Published Nov 16, 2021 · Updated Sep 17, 2024
Cryptographic weakness in AMD 1st, 2nd, and 3rd Gen EPYC processors allows attackers to recover persistent platform private keys. The ASP persistent-storage export path encrypts different fixed-format state blobs with AES-CTR under the same key and fixed initialization vector, allowing ciphertext pairs to reveal plaintext. The demonstrated recovery requires control of persistent storage and a known plaintext-ciphertext pair, and it exposes confidentiality without altering platform state.
Summary
What happened
Cryptographic weakness in AMD 1st, 2nd, and 3rd Gen EPYC processors allows attackers to recover persistent platform private keys. The ASP persistent-storage export path encrypts different fixed-format state blobs with AES-CTR under the same key and fixed initialization vector, allowing ciphertext pairs to reveal plaintext. The demonstrated recovery requires control of persistent storage and a known plaintext-ciphertext pair, and it exposes confidentiality without altering platform state.
The record
- CVE
- CVE-2021-26322
- Published
- Nov 16, 2021
- Updated
- Sep 17, 2024
- Vendor
- AMD
- Product
- 2nd Gen AMD EPYC Processors
- Classifications
- CWE-320, T1552.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 16, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
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