Quote from: Mike Dyer on May 12, 2020, 16:37:22How can it be Microsoft's issue when they're attacking hardware and messing with Intel's security feature? And the mitigation requires specific hardware and BIOS support? Indeed Macs are also vulnerable. Especially under Boot Camp as it seems Apple decided to disable the protection when using Boot Camp. Windows feature the necessary support, just like MacOS or Linux. All of them released it last year.
Sound more like Microsoft Software issue to me. If Its not a problem for Macs Microsoft need to sort themselves out.
Quote from: Thinkpad Fan on May 12, 2020, 04:52:44Unless you actually actively scramble the memory, it's going to take time for the modules to lose their content. It's not instantaneous. And even if they do, it won't entirely protect you. The attack is still relevant.
This isn't even a concern if you have a proper business machine and just enable chassis intrusion detection. The second the bottom cover is removed, the machine will power off and the memory will go blank. Looks like the bad actor can't hack any competently configured devices.
Quote from: Thinkpad Fan on May 12, 2020, 04:52:44Defeating physical tamper protection switches is easy for a skilled attacker. Worst case scenario, bad actor will cut the chassis around the switches - they most likely need not reassemble the machine after they're done extracting data from it.
This isn't even a concern if you have a proper business machine and just enable chassis intrusion detection. The second the bottom cover is removed, the machine will power off and the memory will go blank. Looks like the bad actor can't hack any competently configured devices.
Quote from: Thinkpad Fan on May 12, 2020, 04:52:44The chassis is opened to re-programme the SPI flash chip. Once it's done, the secure level of the thunderbolt controller will be set to zero thus allowing DMA attack.
This isn't even a concern if you have a proper business machine and just enable chassis intrusion detection. The second the bottom cover is removed, the machine will power off and the memory will go blank. Looks like the bad actor can't hack any competently configured devices.
Quote from: King on May 11, 2020, 18:33:38No, the fix is only partial. Full fix should require hardware mitigation not yet available (Intel is planning further mitigation in future hardware). Also, it requires BIOS support. Even among newly released laptops, not all are expected to offer this feature (indeed it seems few do). Not to mention there are known compatibility issues (it requires driver support). So, your hardware might stop working. And it might turn out down the road that this mitigation isn't invulnerable itself. It's not the first attempt at securing Thunderbolt. They might find a way to circumvent it. That's how it goes in security. It's endless battle. The only sure way to prevent misuse is to not have it in the first place. Direct memory access is very powerful and therefore desirable. Not that I'm buying Microsoft's story that they omitted TB3 out of security concerns. It's just a basic principle. It's called reducing attack surface. You can't attack what's not there. I'm sure the glued case on the Laptop was also a security feature - tamper evident. ;-)
But this is fixed on post-2019 laptops, correct? Is there a reason why MS can't implement the fix, whatever the fix is, on their 2020 device??
Quote from: t4n0n on May 11, 2020, 19:16:37Well, you seem to be naive. You're not trying to steal files from RAM, you're trying to steal keys which then allow you to decrypt files. Disk encryption is primarily designed to protect data at rest. Not in use. Standard sleep is not really rest. It's partially on. Not to mention modern stand-by. And spoiler alert, there are attacks even for fully powered down devices. When attacking encryption, it's usually not the mathematics you're targeting. That part tends to be very solid. It's the implementation, the technicalities that are weak. For example, in full disk encryption, you need a key to boot a system. Usually, authentication is happening after boot. That is a very obvious complication in an otherwise good idea to encrypt the whole thing.
I'm sorry, but I've seen this story carried elsewhere on consumer tech sites and a lot of it seems hopelessly naïve.
Like for example the idea attackers could steal your information, even from encrypted files, using this exploit. How, exactly? Unless this has fundamentally changed cryptography as we know it, encryption still renders files unreadable.
I suspect the actual idea here is that an attacker could read the decrypted contents of an encrypted file on disk, that has been opened and is therefore present in memory (through Thunderbolt's DMA) but this, of course, relies on the file being open in the event anyway, at which point, you're only so many steps away from seeing it on the screen.