Virtualization, Cloud, Infrastructure and all that stuff in-between

As the Hoff posts here and on VMTN here. the proposed vulnerability that you can manipulate and possibly compromise a VM during a VMotion process isn’t exactly major, it’s clever.. but – like anything if you don’t follow the best-practice recommendations then you expose yourself to these risks… same reason they recommend you lock your server room or don’t have blank passwords – this attack is akin to gaining physical access to the hardware or being able to sniff a physical switch port – in this instance, it’s “virtual” hardware.

VMWare have always recommended keeping the VMotion traffic on a separate VLAN or network.

the other vulnerability where VMTools can be compromised on is different, but again preventable.. and not enabled on server instances of VMWare.