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
- OpenFaaS: Serverless for Containers Made Easy - October 18, 2017
- Just Say No To KRACK - October 16, 2017
- One USB-C Hub to Rule Them All - October 16, 2017
- How to Accept Email Based Payments for Free as a Freelancer - October 13, 2017
- Satyamania: Windows Subsystem for Linux - October 13, 2017
- Technical Debt in the Age of AI - October 12, 2017
- The Origins of Premises - October 11, 2017
- Technical Debt Really Isn’t All That Bad – The On-Premise IT Roundtable - October 10, 2017
- E Tu Pluribus Networks UNUM? - October 9, 2017
- The Life and Death of Digital Re-Presentations - October 6, 2017