TL;DR
This paper critically analyzes AMD SEV's remote attestation, revealing vulnerabilities in the current firmware that allow attackers to bypass security, and proposes design improvements for future SEV versions.
Contribution
It uncovers critical firmware vulnerabilities in AMD SEV on Naples CPUs and proposes robust design changes to enhance security against malicious cloud providers.
Findings
Extraction of critical CPU-specific keys is possible.
Current firmware versions do not prevent installation of vulnerable firmware.
Attacks can fully circumvent SEV protections.
Abstract
Customers of cloud services have to trust the cloud providers, as they control the building blocks that form the cloud. This includes the hypervisor enabling the sharing of a single hardware platform among multiple tenants. AMD Secure Encrypted Virtualization (SEV) claims a new level of protection in cloud scenarios. AMD SEV encrypts the main memory of virtual machines with VM-specific keys, thereby denying the higher-privileged hypervisor access to a guest's memory. To enable the cloud customer to verify the correct deployment of his virtual machine, SEV additionally introduces a remote attestation protocol.This paper analyzes the firmware components that implement the SEV remote attestation protocol on the current AMD Epyc Naples CPU series. We demonstrate that it is possible to extract critical CPU-specific keys that are fundamental for the security of the remote attestation…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Code & Models
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
