AHV's guest-to-host escapes are inherited: because it uses QEMU device emulation, the escape bugs are the QEMU device-model ones, so fingerprinting the AHV build to its QEMU version and matching a QEMU device advisory is the approach. The vulnerabilities specific to Nutanix instead cluster in the platform services:
- QEMU device models (inherited): virtio, NIC, storage, and USB bugs as on QEMU known escape exploits; the version mapping carries over.
- Prism and the APIs: authentication bypasses, injection, and access-control flaws in the Prism Element/Central interfaces and the REST APIs, giving management-plane compromise.
- Controller VM services: flaws in the CVM-hosted services and their inter-CVM communication, giving CVM or cluster compromise.
Using the pattern#
# fingerprint the AHV and platform version
ncli cluster info 2>/dev/null | grep -i version
# guest side: confirm the QEMU-emulated devices present (inherited surface)
lspci -nn; lsusb
Fingerprint the AHV/QEMU version for the inherited device surface, and the Prism/AOS version for the platform surface, then match to the relevant advisory. The device escapes are version-specific QEMU bugs; the platform bugs are Nutanix security advisories.
Exploitation notes#
- For a guest-to-host escape, treat AHV as QEMU: the mechanisms and version mapping are the QEMU ones on the guest-to-host escape page.
- The distinctly-Nutanix bugs are in Prism and the CVM services; those give management-plane or Controller-VM compromise, which (via the storage fabric) reaches every VM's data without a guest escape at all.
- Check both version surfaces: the QEMU version for device escapes and the AOS/Prism version for platform vulnerabilities.