hn.today

It's time to talk about TEEs

alinush.github.io18 points6 comments
Screenshot of It's time to talk about TEEs

The piece surveys a series of practical and academic attacks that collectively undermine the security assumptions of trusted execution environments (TEEs). It groups failures into classes: bugs in enclave code (e.g., Signal’s SGX-based contact discovery leaking memory), remote attestation forgery and key-extraction attacks (Foreshadow 2018, SGAxe 2020, ÆPIC Leak 2022), and a recent wave of physical DRAM interposition attacks and memory tampering (BADRAM2, WireTap.fail, TEE.fail, Battering RAM, DDRrop across 2024-2026) that extract or falsify attestation material or enable backdoored VMs. The write-up emphasizes that remote attestation verifiers that accept any “good” CPU can be deceived by an attacker who compromises one platform, and that the only practical defense is tightly pinned PKI management for attestation keys - an operational footgun for most deployments.

It also highlights liveness and availability problems: credential revocations and slow TCB recovery have left enclaves unusable in past incidents, and denial-of-service remains explicitly out of the threat model for many TEEs. Many academic attacks further expand the threat surface. The practical takeaway is blunt: do not place high-value secrets in TEEs unless you accept significant risk or are willing to sacrifice performance and functionality for more principled, lower-level designs.

Read on alinush.github.io6 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Security

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.