Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Security Encryption Privacy

Bootkit Bypasses TrueCrypt Encryption 192

mattOzan writes with this excerpt from H-online: "At Black Hat USA 2009, Austrian IT security specialist Peter Kleissner presented a bootkit called Stoned which is capable of bypassing the TrueCrypt partition and system encryption. The bootkit uses a 'double forward' to redirect I/O interrupt 13h, which allows it to insert itself between the Windows calls and TrueCrypt."
This discussion has been archived. No new comments can be posted.

Bootkit Bypasses TrueCrypt Encryption

Comments Filter:
  • Uh, what? (Score:5, Interesting)

    by Cthefuture ( 665326 ) on Saturday August 01, 2009 @07:52PM (#28912893)

    So yeah, if someone is running live software on your machine then there isn't much you can do. If there is decrypted data then it's essentially available to anything on the machine.

    I mean if you're going to do this you could just modify the TrueCrypt code (bootloader in this case) itself to do what you want.

    Kind of "duh" story if you ask me.

  • by Wrath0fb0b ( 302444 ) on Saturday August 01, 2009 @08:03PM (#28912943)

    TFA has a very good point -- unless you (cryptographically) trust the components of your system all the way down to the hardware itself, you can get pwned by an attack like this. You can regularly do all-the-way-to-the-firmware scrubs of your machine as damage-control, but the only real prophylactic is some form of trusted computing.

    Of course, I'm not really dying to jump on the TPM bandwagon, given the sponsors, but it sure would be nice if there was an openly-audited trusted computing module.

  • by dnaumov ( 453672 ) on Saturday August 01, 2009 @08:50PM (#28913233)

    If someone can gain physical access to your machine then it's effectively game over.

    If that was the case, what would be the point of disk/partition encryption in the first place?

  • Re:Uh, what? (Score:3, Interesting)

    by The MAZZTer ( 911996 ) <.moc.liamg. .ta. .tzzagem.> on Saturday August 01, 2009 @08:53PM (#28913239) Homepage
    Well, I assume the entire system is encrypted, in which case there'd be little you COULD do except trick the user into giving you their decryption key.
  • by CharlyFoxtrot ( 1607527 ) on Saturday August 01, 2009 @09:28PM (#28913395)

    Is this type of attack only limited to trucrypt or can it affect other product?

    From what I understand it could potentially affect other products unless they (properly) use TPM to avoid this kind of attack by checking MBR against a checksum.

    is there a way to prevent it?

    Get a mac! Not trolling, from TFA: "The attack is unsuccessful when the BIOS successor the Extensible Firmware Interface (EFI) is at work on the motherboard." AFAIK Apple are the only vendor using EFI on their entire range at the moment. I guess mounting everything read-only, or using a BSD with the file immutable bit [cyberciti.biz] set on all system files would work too.

  • by sumdumass ( 711423 ) on Saturday August 01, 2009 @09:56PM (#28913501) Journal

    I'm not so sure a mac is the answer. With a mac, you can just install the code in the keyboard [slashdot.org] and grab the keys directly.

  • by khayman80 ( 824400 ) on Saturday August 01, 2009 @09:56PM (#28913507) Homepage Journal

    You're absolutely right. Strangely, none of those links led to Peter Kleissner's web page [peterkleissner.com].

    Check out the comments. Some of the visitors are flaming him pretty hard, but he's just a kid with amazing skills and (understandably) very little historical knowledge. Luckily, Christian [peterkleissner.com] politely points out that his attack serves to "... alert many people who think they made their PC secure by installing TrueCrypt and still keep working with an admin account where they should not. You prove that a security policy is indispensable, because admin privileges will give malicious software the ability to tamper with the installed security software."

  • by buchner.johannes ( 1139593 ) on Saturday August 01, 2009 @09:58PM (#28913517) Homepage Journal

    This exploit really is more comparable to a software keylogger. It lies between OS and Truecrypt Bootloader, catching the disk access requests.
    For infection, you need admin rights on the running machine (TFA says so).

    So, with the full system encryption, you are of course safe. This is just a way of listening to Truecrypt requests.

    Kudos to Peter, hope to meet him in the Metalab sometime.

  • by ehrichweiss ( 706417 ) * on Saturday August 01, 2009 @10:18PM (#28913587)
    Encryption is to prevent your data from escaping if someone stole your laptop. It however will NOT prevent the thief from installing a keylogger(which is what TFA is basically describing) which can then be used to discover your passphrase and eventually gain access to the system.

    If you lose a laptop and then recover it, you can be fairly certain that your data was never leaked but you cannot be certain that someone didn't tamper with your system so they could steal the data later. At that point the best you could do would be mount the volume on a completely different system and move any data you hadn't already backed up, then wipe the drive/bios fully..though after yesterday's article about the BIOS "rootkit" that is Computrace, I'd be wary of the hardware at that point.
  • Funny, but true (Score:3, Interesting)

    by Sycraft-fu ( 314770 ) on Saturday August 01, 2009 @10:35PM (#28913641)

    Things like encryption are to protect against normal problem, like losing a device with important data, not to protect against a determined adversary that wants your particular stuff.

    For example I have an encrypted USB stick who's function is to hold my passwords, in particular the ones I don't use a lot. It is a USB stick, since I don't want to keep something like that on my computer which is always networked. While I think I have good security, there's always a chance someone owns my computer and I don't notice. So, best not to keep passwords on it. It is encrypted in case I ever lose it, or it gets stolen. That way, the person who has it can stumble across the password text file.

    That is what it is to protect against: Normal ways that someone might happen across my passwords. It is not a protection against everything. If someone really wanted my passwords, they could just hold a gun to my head, I'd give them what they wanted. Nothing I have is worth dying for. As such, no amount of protection would keep it safe. I don't bury my key in a hidden location, I don't keep its existence a secret, etc. Reason is none of that would matter since anyone willing to go to the lengths necessary to get at it, would be willing to go to the lengths to get at me and make me give up my passwords.

    Full disk encryption isn't for universal protection, it is for protection against laptop theft. For example at work we used to have an idiot in charge of, among other things, issuing codes for the doors. Our doors have electronic keypad locks as well as physical locks. Ok so idiot didn't keep this data on the central servers. He didn't trust it there. He instead kept it on his laptop. Well, his laptop then got stolen, and the data wasn't encrypted. That was a lot of fun, we got to change all the door codes. Had he encrypted his disk, this wouldn't have been a problem. The crook wasn't trying to get our door codes, they were just stealing a laptop.

  • by mlts ( 1038732 ) * on Saturday August 01, 2009 @11:06PM (#28913727)

    The tools are there (tboot, TrouSers). What is missing is a gestalt "stack", where an admin can configure a distro to "seal" the hash of various parts of the boot process in the TPM (MBR, boot sector, BIOS, kernel, RAMdisk image), then encrypt the rest of the machine. Then, at boot, it would boot to the ramdisk filesystem, ask the TPM for the key, and if the image has not been tampered with, the TPM will hand the key over, and the boot process continues.

    One thing that isn't discussed (which is important) is a facility for recovering the encrypted data should the TPM be off or erased. BitLocker handles this fairly gracefully by saving a keyfile to a USB flash drive, or allowing the user to print out a sequence of numbers with the recovery key. BitLocker also allows saving of the recovery key to Active Directory, ensuring that corporate IT has recovery access (which is required by law in a number of cases). Finally, for home users, BitLocker allows use of offsite storage for the recovery information.

    Another option to implement a means of recovery is to have a recovery passphrase. PGP is a product that allows this, where one can boot from a TPM, but if that is unavailable, one can type in a previously set passphrase, or a WDRT (whole disk recovery token, which is a challenge/response system).

    This functionality will have to be implemented distribution by distribution, as there isn't a standardized set of tools. Perhaps one thing that should be designed would be a standard for implementation across distros.

  • Re:LFP is doomed (Score:1, Interesting)

    by Anonymous Coward on Saturday August 01, 2009 @11:37PM (#28913879)

    You replied, off-topic, to the first off-topic post, which was also a troll, over ten minutes after this [slashdot.org] and this [slashdot.org] top-level ones, which coincidentally say the exact same thing as yours.

    It didn't take ten minutes to type that, didn't it?

    It's really sad that your karma whoring works.

  • by myforwik ( 1465003 ) on Saturday August 01, 2009 @11:49PM (#28913921)
    Just boot from a CD rom. Infact forget the hash, just boot from the truecrypt rescue disk every time which restores your MBR.

Old programmers never die, they just hit account block limit.

Working...