Windows 8 Bootkit Exploits User Account Control

November 28, 2011
27
Views

completely bypasses the UAC and does not alert the end user whatsoever. This new bootkit doesn’t actually seem to be a bootkit made from scratch, it’s more of an extension on the Stoned bootkits that Kleissner had made for previous versions of Windows such as Windows XP, Windows Vista, and Windows 7 as well as Windows Server 2003. Windows 8 Bootkit Demo from Peter Kleissner on Vimeo. Even though this bootkit has been made for other versions of Windows, for Windows 8 it just seems more significant. For one, Windows 8 is supposed to be a lot more secure than its previous versions, and for the most part, it is. But if this bootkit shows us anything, it shows that Microsoft still has a lot of work to do ahead. Which is to be expected for an operating system that is so early in development. I am actually surprised that Windows 8 is as secure as it is, I don’t think any other operating system could work this well so early into development, but that is probably why they released it to the general public, for free. Though of course on a side note, only people that are tech savy would be brave enough to install an operating system on their computers, let alone one that isn’t even finished. Microsoft will probably deal with the vulnerabilities found by Kleissner by the time of next year’s (or possibly the year after that’s) Windows 8 launch, but for now, there isn’t much to be worried about. Stoned (or Stoned Lite as it’s Windows 8 version is called) requires a BIOS to actually run at start-up. It can run as its own application on the desktop, but that wouldn’t have much effect on the machine because the user would have to start the bootkit themselves. So basically SecureBoot is actually doing what it’s supposed to do, prevent rootkits, bootkits, and other unauthorized executable files from running at start-up. Kleissner himself even cited the problem with the BIOS while talking to Softpedia, “The problem with the [BIOS] is that no one verifies the MBR, which makes it the vulnerable point. With UEFI and secure boot, all the boot applications and drivers have to be signed; otherwise they won’t be loaded.” Source 1 Source 2]]>

Article Tags:
· · · ·
Article Categories:
Microsoft

Mike Johnson is a writer for The Redmond Cloud - the most comprehensive source of news and information about Microsoft Azure and the Microsoft Cloud. He enjoys writing about Azure Security, IOT and the Blockchain.

Leave a Reply

Your email address will not be published. Required fields are marked *