Memory-integrity loss via unvalidated SEV commands
Published Nov 16, 2021 · Updated Sep 16, 2024
Improper input validation in AMD SEV firmware on 3rd Gen AMD EPYC processors allows local users to compromise SNP memory integrity. The SEV firmware fails to validate SEV commands submitted while Secure Nested Paging is active, allowing invalid command data to affect protected memory state. Exploitation requires local low-privileged access on a system actively using SNP; the published consequence is limited to memory-integrity loss.
Summary
What happened
Improper input validation in AMD SEV firmware on 3rd Gen AMD EPYC processors allows local users to compromise SNP memory integrity. The SEV firmware fails to validate SEV commands submitted while Secure Nested Paging is active, allowing invalid command data to affect protected memory state. Exploitation requires local low-privileged access on a system actively using SNP; the published consequence is limited to memory-integrity loss.
The record
- CVE
- CVE-2021-26323
- Published
- Nov 16, 2021
- Updated
- Sep 16, 2024
- Vendor
- Advanced Micro Devices, Inc.
- Product
- 3rd Gen AMD EPYC Processors
- Classifications
- CWE-20
- 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 <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.
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