Re:How the NSA’s Firmware Hacking Works and Why It’s So Unse...
by chirayuk on Monday February 23, 2015 @12:09AM
(#9092657)
Some thoughts: VMs are an interesting case. Someone with the motive and means would have exploits to get out of the VM. This is probably easier if the guest is running something to accelerate (e.g. VMWare Tools / VirtualBox Guest Additions.) Once you get out, you have to account for the host OS. Assuming you could do it, how does one determine if the VM is part of a honeypot or the target?
Re:How the NSA’s Firmware Hacking Works and Why It’s So Unse...
by temp0larry on Monday February 23, 2015 @07:06AM
(#9093839)
Not really. Consider how many hypervisors are there really to exploit from a virtual OS?
Maybe four.
HyperV, KVM, ESX, what you mentioned, etc...
But really, 3 vendors - Oracle, Microsoft, and VMWare covers the majority.
Way fewer virtualization technologies (mainstream) than hard drive firmwares.
If the VM is using an emulated disk based on an image file on the host, probably no chance at all as only "read block" and "write block" types of commands will be interpreted by the virtual disk. Even other mundane commands like "spin down to save power" won't make it to the hardware due to the effect that would have on the host or other VMs on it.
If the VM is configured to passthrough directly to the hardware, then it has full control over the HDD.