Practical Ghostbusting: Meltdown, Spectre and You
summary
Explains how Meltdown breaks hardware isolation by exploiting out‑of‑order execution and cache timing to read kernel and DRAM one byte at a time, while Spectre poisons branch prediction to leak secrets across processes and devices and can be triggered via JavaScript on unpatched browsers. Details required mitigations: OS patches, CPU microcode updates, browser fixes, and runtime changes; notes performance hits varying from a few percent up to ~20–30% and that researchers published 130 proof‑of‑concept variants discovered.
AI-written summary · about
chapters (10)
- 0:00PRACTICAL
- 6:11MELTDOWN AND SPECTRE
- 8:50SOFTWARE IS
- 11:54SPECULATIVE EXECUTION
- 13:55BRANCH PREDICTION
- 15:30SIDE CHANNEL ATTACKS
- 16:17HOW DID THIS HAPPEN?
- 23:52Spectre's name is based on the
- 33:12FIRST, SOME REALISM
- 46:22MITIGATION
related talks
25mThe Memory of a Meltdown
24mThe Memory of a Meltdown
30mSpectre, Meltdown, & Linux
01h 28m“Spectre: Secrets, Side-Channels, Sandboxes, and Security”
43m“Closing Panel: Spectre”
51mExploiting Hardware Glitches And Side Channels In Perfect Software
48mSpeculative execution vulnerabilities
23mMeltdown: Reading Kernel Memory from User Space