The virtual machine escape demonstrated at Pwn2Own this year showed that for even as isolated software defined machines, VMs are not without there security concerns. Andrea Mauro took this as inspiration to reflect on some of the other vulnerabilities. Virtually networking is probably the most common, as the guest machines as vulnerable as any other to these kind of exploits. These are mitigated by the supposed isolation each machine enjoys. Andrea does point out though that any time you have shared components between machines, you introduce the possibility of mitigating the virtual machines inherent estrangement.
It goes to show that the old tradeoff of security vs convenience applies equally as well to the virtual machine world as to the physical one.
Andrea Mauro comments:
Recent VMware security bug (VMSA-2017-0006) is related to one of the worst possible security issue in a virtualization environment: a possible “guest escape” vulnerability that allows arbitrary code execution on a host system from the guest system. It’s not the first time of a similar risk (see, for example, Microsoft Edge used to escape VMware Workstation at Pwn2Own 2017) but this kind of issue is a different risk level if it affect Worksation (so “just” a client environment) or a ESXi (potentially a datacenter environment).
Read more at: How a VM is really isolated
- Robin Systems Defines Applications - May 26, 2017
- Sans SAN with StorMagic - May 25, 2017
- VMware NSX: Going Big with Micro-Segmentation - May 23, 2017
- DNA Storage is Weird - May 23, 2017
- NetApp and Open Source - May 23, 2017
- What is Big Data? The On-Premise IT Roundtable - May 23, 2017
- NAS Effect: 10TB Western Digital Red Drives - May 22, 2017
- Intel NFV, an SD-WAN Cook-Off, and a Missing Control Plane in Gestalt Networking News 17.6 - May 22, 2017
- “Big Data” Isn’t a Thing - May 19, 2017
- Managed Storage with ClearSky Data - May 19, 2017