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
- AMD Plays the Long Hygon | Gestalt IT Rundown: July 11, 2018 - July 12, 2018
- AIRI: Converging FlashBlade into an AI Reference Architecture - July 12, 2018
- 2018 MacBook Pros Comes Closer to Earning Their Name - July 12, 2018
- The Path of an IT Influencer Starts with a Single Post - July 12, 2018
- Leon Adato – IT Origins - July 10, 2018
- John Welsh – IT Origins - July 5, 2018
- Covering All Your Storage Bases - June 28, 2018
- WPA3 Is Certifiable | Gestalt IT Rundown: June 27, 2018 - June 27, 2018
- IT Burnout is Inevitable – The On-Premise IT Roundtable - June 26, 2018
- Oksana Sokolovsky – IT Origins - June 21, 2018