Cold boot attacks: what RAM remembers after the power is cut
Turning a computer off feels like a hard boundary. It is not. The DRAM that holds a running system's working memory is a grid of tiny capacitors, and capacitors discharge gradually. For seconds, sometimes minutes, after power disappears, the chips still hold most of what was written to them, including the volume keys that full-disk encryption loads at boot. An attacker who restarts such a machine with a minimal bootloader and copies out the leftovers can walk away with those keys. That is a cold boot attack, and it has been demonstrated against real, widely used encryption products since 2008.
The Princeton work that named the problem
The canonical demonstration came from researchers at Princeton University's Center for Information Technology Policy and their collaborators. Their paper, 'Lest We Remember: Cold Boot Attacks on Encryption Keys,' was presented at the USENIX Security Symposium in San Jose in July 2008. The gap between then and now is worth stating plainly: the technique is old, and so is the warning. The authors showed that DRAM retains its contents for seconds to minutes after power loss, even at operating temperatures and even after modules are pulled out of the motherboard, and that simple cooling, which the team applied with spray coolant, stretches that window dramatically. Using no special devices or materials, they recovered disk encryption keys from memory images and defeated BitLocker, FileVault, dm-crypt and TrueCrypt in cold reboots. They also described algorithms for locating keys in partially decayed memory and correcting the bit errors.Why the keys survive
AES key schedules are the weak point. The expanded key is stored in memory with heavy internal redundancy, so even a noisy dump can be corrected to the true key. And modern hardware does not close the hole. A 2017 academic analysis, 'Cold Boot Attacks are Still Hot: Security Analysis of Memory Scramblers in Modern Processors', examined the scrambling logic that contemporary processors apply to DRAM, a measure often assumed to blunt these attacks, and found it ineffective: the scrambling mask can be derived from the dumped data itself. The authors built a proof of concept that recovers an AES disk encryption key from a modern processor's memory, and their attack relies on a brief power interruption rather than on chilling the modules.Why shutdown is not safety
If keys were reliably erased at shutdown, the window would be small. But several common power states never erase anything. Suspend-to-RAM keeps the DRAM powered and refreshed: every key the system was holding stays put, behind a lock screen that can be attacked directly. Hibernation writes the RAM image to disk instead, which is only as safe as the encryption on the swap or hibernation volume, since a snapshot of running memory on unencrypted storage is a gift. Even a warm restart does not cut power to the modules for long. The Tails project, which documents this threat for its users, puts the exposure plainly:... can remain in RAM up to several minutes after shutdown ...That warning is aimed at ordinary laptops. A machine that is off in the casual sense, lid closed and screen dark with the power state fuzzy, may still be holding everything an attacker wants, and grabbing it costs seconds.
What mitigations actually exist
Tails is the most visible defense in daily use. At shutdown the system overwrites most of its RAM with random data, and the same erasure fires when the boot medium is physically pulled during runtime, an emergency path built for exactly the moment someone grabs the machine. Under the hood it relies on the kernel's init-on-free feature plus a watchdog that monitors the USB medium, and the design notes add that files the wipe process needs are locked into memory from boot so the erasure cannot be pushed out while it runs. The habits that pair with this are unglamorous but concrete:- Power off fully instead of suspending, especially before handing a device to anyone else.
- Learn the fastest shutdown path on your system, because the wipe takes time to run.
- Never leave a running or suspended laptop physically unattended.
- If hardware leaves your sight in a high-risk setting, treat it as possibly tampered with, not merely switched off.