09-20-12 | Blog Post
On September 6th, Threatpost.com reported on an exploit regarding a vulnerability in Xen hypervisors that caused a virtual machine escape. The vulnerability stems from the way intel processors are implementing error handling on a specific instruction within the Xen hypervisor.
This is allowing users to gain privileged access to the VM Dom0, which is the only VM that by default has the ability to interact with the hardware. After getting this privilege, a user could then execute code from Dom0 that could affect any and all other VMs within the hypervisor.
This vulnerability was brought up and patched in June, but a new exploit occurred just last week based on the same issue.
So, why is this such a dangerous exploit? Well, it underlines an inherent flaw in the design of the Xen hypervisor. Anyone looking for a multi-tenant solution for their hosting could really have to deal with some problems that spread across several companies, and because the flaw is built-in, it’s a weak point that could continue to be exploited over and over again.
VMware, another hypervisor, doesn’t have this vulnerability because its setup does not have a VM with access to the hardware, making it a safer option when determining what solution works best for your business.
In short, when shopping around for a shared cloud solution, or if you have an IaaS structure for your company, your hypervisor’s architecture is an important point to research in order to sidestep some potentially serious security issues.