Cold Reboot Attacks on Disk Encryption 398
jcrouthamel writes "Contrary to popular assumption, DRAMs used in most modern computers retain their contents for seconds to minutes after power is lost, even at operating temperatures and even if removed from a motherboard. Although DRAMs become less reliable when they are not refreshed, they are not immediately erased, and their contents persist sufficiently for malicious (or forensic) acquisition of usable full-system memory images. We show that this phenomenon limits the ability of an operating system to protect cryptographic key material from an attacker with physical access. We use cold reboots to mount attacks on popular disk encryption systems — BitLocker, FileVault, dm-crypt, and TrueCrypt — using no special devices or materials. We experimentally characterize the extent and predictability of memory remanence and report that remanence times can be increased dramatically with simple techniques. We offer new algorithms for finding cryptographic keys in memory images and for correcting errors caused by bit decay. Though we discuss several strategies for partially mitigating these risks, we know of no simple remedy that would eliminate them."
Physical Access (Score:3, Insightful)
1) They have your desktop computer
2) It is on
3) You've entered your crypto keys
Is it me or is this just a little tenuous? In a data centre they'd have to drag the thing off the rack and on your personal machine they'd have to physically take it off you, because waiting for you to shutdown and then walk-away would be too long. So the solution is to shutdown the machine and THEN put your coat on and pack your bag.
I can also get people's Crypto keys by threatening them with a knife or putting a CCTV camera over their workstation. There are "easier" ways to get the keys if you have physical access to the environment that are much simpler and reliable.
Re:Clear the DRAM? (Score:5, Insightful)
Re:only useful if you start off unencrypted (Score:3, Insightful)
Use capacitors (Score:5, Insightful)
from an attacker with physical access (Score:4, Insightful)
Re:Clear the DRAM? (Score:3, Insightful)
Really, though, who would this affect? Top secret government stuff. I bet they've just got vials of acid or explosives or something. Tamper with the case and the contents (and maybe you) go bye-bye.
Re:only useful if you start off unencrypted (Score:2, Insightful)
Re:Physical Access (Score:5, Insightful)
Like when your laptop is stolen while it's in sleep mode. This is rather a common situation.
I can't believe this hasn't been mentioned... (Score:3, Insightful)
we know of no simple remedy that would eliminate them...
As part of a secure programming course I recently took, we were instructed to overwrite keys with zeros when done using them. It's that simple - you don't leave the key in memory for any longer than you need it.
When the machine is powered down, your application's exit routine zeros all of the memory, and then free()s it. Nothing that good programming practices can't address.
Generally speaking, it's the keys on the disk(!) that are the problem. Without two factor authentication, you need merely to scan disk sectors...
Dirty fix (Score:2, Insightful)
Password the BIOS, boot only from local disk.
Re:Clear the DRAM? (Score:5, Insightful)
That being said, some sort of physical security mechanism probably wouldn't be out of the question for scenarios that actually called for it. For instance, on systems that contain highly sensitive data such as nuclear launch codes or some such, I could envision a tripwire type system on the computer case that detonates shaped charges on the HD and RAM when the case is cracked. This does open up a possible DOS attack vector, but the alternative seems to justify it.
Re:Physical Access (Score:1, Insightful)
Re:Hardly the problem (Score:3, Insightful)
Simple fix, no? (Score:4, Insightful)
Wait, doesn't it already?
Wait, did the researchers bypass BIOS?
Well, if they did, then adding some crap to DRAM to kill it on power loss is the only way. Probably.
It was once an axiom of system security, that if you gained physical access, all was lost. This evolved from keyboard and console attacks to floppy- and CD-boot attacks, USB keys, stealing the hard drive, you know the drill.
Ultimately, if you can cart away pieces of the machine, your last line of defense is gone.
The only other variable to control is time. Make the DRAM die quicker, or is it time for a 'better' memory technology?
And this is such great stuff, the TEMPEST guys will now have to re-write their procedures, with both a power-off and wait 30 seconds, and a re-power-on and wait for login prompt, then shutdown again.
Sometimes I hate h@xrs, and sometimes I realize they do me a service, albeit while they intend to just do me.
How ironic. My captcha is 'honest'. This cannot be coincidence.
DRM attack vector (Score:5, Insightful)
Re:I can't believe this hasn't been mentioned... (Score:4, Insightful)
Unless of course the machine is, you know, simply "powered down".
Pulling the plug isn't going to let your application do squat.
This is pretty epic... (Score:4, Insightful)
Re:I can't believe this hasn't been mentioned... (Score:3, Insightful)
Re:Physical Access (Score:3, Insightful)
Re:Clear the DRAM? (Score:5, Insightful)
Re:Very real concern (Score:1, Insightful)
Epoxy (Score:3, Insightful)
It seems like the best defense would be applying epoxy to the memory so it couldn't be removed from the slot. If you make sure all the connections are covered as well, they wouldn't be able to place a tap, either. (At least without a lot of time being spent slowly drilling through the epoxy.)
It would make it impossible to replace your memory, but you could always move the HD to another system. If you care that much, then you should be willing to pay for a new system if someone tries to compromise your data.
this seems must useful as a way to crack DRM (Score:2, Insightful)
Re:Clear the DRAM? (Score:4, Insightful)
BTW, since you claim to be using (presumably US) government security software, you know that disk formatting or dd if=/dev/zero of=/dev/whatever is not sufficient to unclassify a disk that formerly contained classified material.
Re:Already Screwed (Score:2, Insightful)
Re:Clear the DRAM? (Score:3, Insightful)
And any way you slice it, feeling secure has little to do with being secure (TSA, are you listening?) although I have noticed that people who feel secure are generally at the most risk. Mainly, I suppose, because they don't have the knowledge to properly assess the risks they are accepting. Because if they did
If you want to be as secure as you possibly can, start with the assumption that you're not.