HackerPapers

arXiv:2004.11071cs.CR

SEVurity: No Security Without Integrity -- Breaking Integrity-Free Memory Encryption with Minimal Assumptions

Luca Wilke, Jan Wichelmann, Mathias Morbitzer, Thomas Eisenbarth

Abstract

One reason for not adopting cloud services is the required trust in the cloud provider: As they control the hypervisor, any data processed in the system is accessible to them. Full memory encryption for Virtual Machines (VM) protects against curious cloud providers as well as otherwise compromised hypervisors. AMD Secure Encrypted Virtualization (SEV) is the most prevalent hardware-based full memory encryption for VMs. Its newest extension, SEV-ES, also protects the entire VM state during context switches, aiming to ensure that the host neither learns anything about the data that is processed inside the VM, nor is able to modify its execution state. Several previous works have analyzed the security of SEV and have shown that, by controlling I/O, it is possible to exfiltrate data or even gain control over the VM's execution. In this work, we introduce two new methods that allow us to inject arbitrary code into SEV-ES secured virtual machines. Due to the lack of proper integrity protection, it is sufficient to reuse existing ciphertext to build a high-speed encryption oracle. As a result, our attack no longer depends on control over the I/O, which is needed by prior attacks. As I/O manipulation is highly detectable, our attacks are stealthier. In addition, we reverse-engineer the previously unknown, improved Xor-Encrypt-Xor (XEX) based encryption mode, that AMD is using on updated processors, and show, for the first time, how it can be overcome by our new attacks.

arXiv comments
14 pages, 6 figures, accepted at IEEE S&P 2020
Journal reference
Proceedings of IEEE S&P, Year 2020, Volume 1, Pages 1746-1759
DOI
doi:10.1109/SP40000.2020.00080
Subjects
cs.CRCryptography and Security

On Hacker News

Linked by 2 identifiable commenters in 3 comments across 2 threads, from Jun 2020 to Jul 2020.

Comments linking this paper, per year.

Discussed in comments2 threads

  1. Confidential VMs 1 comment
    • AMD SEV's mode has changed over time (as AMD moved from SEV, to SEV-ES, to SEV-SNP). Each time, some academic has managed to reverse engineer the mode. This paper (published 2020) has documented the developments and reverse engineered the mode in SEV-ES.…

      ENOTTYView on HNParent context

  2. How SGX Fails in Practice 2 comments
    • SEV has been subjected to its own share of attacks (and design/implementation fails), but note that it has a different threat model. * https://arxiv.org/pdf/1712.05090.pdf 2017 * https://arxiv.org/pdf/1612.01119.pdf 2017 * https://arxiv.org/pdf/1805.09604.pdf 2018 *…

      ENOTTYView on HNParent context

    • Yes - in a recent paper by Wilke et al[0], they nicely demonstrate how the lack of integrity checking can be exploited. SEV is a very new technology and its current (and previous) iterations have known weaknesses. The next generation of SEV will likely have SEV-SNP[1], which…

      limaView on HNParent context

Submitted to Hacker News

Connected through shared HN threads, not inferred similarity or a recommendation.