Guest code execution via permutation-agnostic attestation
Published May 13, 2021 · Updated Sep 17, 2024
Attestation bypass in AMD SEV and SEV-ES allows attackers to execute arbitrary code inside an attested guest VM. The attestation measurement is permutation-agnostic, so a compromised hypervisor can reorder measured guest-memory blocks without changing the reported measurement and can assemble a ROP chain during UEFI startup. Exploitation requires administrator control of the server hypervisor and grants control of the guest operating system despite successful attestation.
Summary
What happened
Attestation bypass in AMD SEV and SEV-ES allows attackers to execute arbitrary code inside an attested guest VM. The attestation measurement is permutation-agnostic, so a compromised hypervisor can reorder measured guest-memory blocks without changing the reported measurement and can assemble a ROP chain during UEFI startup. Exploitation requires administrator control of the server hypervisor and grants control of the guest operating system despite successful attestation.
The record
- CVE
- CVE-2021-26311
- Published
- May 13, 2021
- Updated
- Sep 17, 2024
- Vendor
- AMD
- Product
- AMD Secure Encrypted Virtualization (SEV)
- Classifications
- CWE-77, T1068
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 13, 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 <SEV-SNP
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
- undeSErVed trust attack artifactfunctional · demonstrated
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