A hypervisor runs untrusted guest operating systems and is supposed to keep them isolated from the host and from each other. Offensive work targets the places where that isolation leaks: the device models the hypervisor emulates for guests (the usual guest-to-host escape surface), the management plane that controls fleets of hosts, and the virtual disks and snapshots that hold guest data at rest.
The area is organized by product, because escapes are specific to each hypervisor's device-emulation code, with a consistent set of aspects under each.
Subtopics#
- VMware: ESXi and vCenter, plus the Workstation and Fusion desktop hypervisors.
- Hyper-V: the Windows hypervisor and its management stack.
- VirtualBox: the Oracle desktop hypervisor.
- KVM: the Linux KVM ecosystem: QEMU, the kernel module, Proxmox VE, Nutanix AHV, and the Firecracker and Cloud Hypervisor microVM monitors.
- Xen: the Xen hypervisor and its control domain.
- Parallels Desktop: the macOS desktop hypervisor.
- bhyve: the FreeBSD hypervisor.