Shweta Shinde<p>Can a malicious cloud provider send bad notifications to break confidential VMs?</p><p>Disclosing <a href="https://ioc.exchange/tags/AhoiAttacks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AhoiAttacks</span></a> that break confidential computing offered by AMD SEV-SNP and Intel TDX by abusing interrupt delivery.</p><p><a href="https://ahoi-attacks.github.io/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ahoi-attacks.github.io/</span><span class="invisible"></span></a></p><p>Our first attack <a href="https://ioc.exchange/tags/Heckler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Heckler</span></a> to appear Usenix Security 2024 breaks Intel TDX and AMD SEV-SNP by sending interrupts that trigger existing handlers to change the register state and variables in userspace. We break sshd, sudo, and other apps.</p><p>Our second attack <a href="https://ioc.exchange/tags/WeSee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WeSee</span></a> to appear IEEE Security & Privacy 2024 breaks AMD SEV-SNP by sending an interrupt specially introduced for SEV. Starting from a kernel read to arbitrary code injection, we gain a root shell.</p><p>Track CVE-2024-25742, CVE-2024-25743, CVE-2024-25744 for updates on fixes and patches.</p><p>A fantastic team effort by Benedict M. Schlüter, Supraja Sridhara, Andrin Bertschi, and Mark Kuhne!</p>