CVE-2023-20867: VMware Tools Authentication Bypass Vulnerability
VMware Tools contains an authentication bypass vulnerability in the vgauth module. A fully compromised ESXi host can force VMware Tools to fail to authenticate host-to-guest operations, impacting the…
CVE-2023-20867 is an authentication bypass vulnerability in VMware Tools, specifically within the vgauth module. It allows a fully compromised ESXi host to force VMware Tools to fail authentication for host-to-guest operations, which can impact the confidentiality and integrity of the guest virtual machine. An attacker needs root access on the ESXi host to exploit it. This matters because VMware Tools is commonly installed inside guest VMs to enable management features; a breach of the hypervisor layer can therefore undermine trust boundaries that protect guest systems and their data.
Defenders should treat this as a high-priority issue in any environment running VMware Tools under ESXi, because successful abuse expands the blast radius of an already-compromised host. Confirm all product details and fixed versions against the official VMware advisory.
How it works
The flaw is classified as CWE-287 (Improper Authentication). In normal operation the vgauth module authenticates host-to-guest requests so that only legitimate management actions are accepted by the guest. When the vulnerability is present, an attacker who already holds root privileges on the ESXi host can cause that authentication step to fail open or be bypassed. As a result, unauthenticated or improperly authenticated host-to-guest operations can be forced, allowing the attacker to affect the confidentiality and integrity of the guest virtual machine. No further exploit mechanics are required beyond root-level control of the ESXi host; the vulnerability simply removes an authentication check that should have protected the guest.
Because the prerequisite is full compromise of ESXi, this is not a remote unauthenticated attack from outside the hypervisor. It is a privilege-escalation or lateral-movement enabler once the host is already under attacker control.
Am I affected? How to find it in your systems
VMware Tools typically runs inside guest virtual machines that are managed by ESXi hypervisors. Inventory every virtual machine that has VMware Tools installed—Windows, Linux, and other supported guest operating systems. Check the installed Tools version and configuration against the vendor advisory for the exact builds that contain the vulnerable vgauth module. Look for the presence of the vgauth service or related binaries on each guest.
- Use your configuration-management or asset-inventory tools to list all VMs reporting VMware Tools.
- Query guest operating systems for the Tools package version and the status of the vgauth component.
- Review ESXi host logs and guest logs for anomalous host-to-guest operations that occur without expected authentication success messages.
- Monitor for unexpected changes to guest files, processes, or credentials that could indicate forced host-to-guest activity.
Any environment in which ESXi hosts can be fully compromised is potentially exposed until Tools is updated. Specifics of affected versions must be confirmed against the vendor advisory.
How to remediate
Apply the vendor-supplied updates for VMware Tools as directed in the official advisory. CISA’s required action is simply to apply updates per vendor instructions. After patching, verify that the vgauth module is running the corrected version and that host-to-guest authentication behaves as expected.
- Schedule and deploy the Tools update through your normal change process, preferably via the ESXi host’s update mechanisms or guest package managers.
- Reboot guests if required by the update and confirm Tools services restart cleanly.
- Harden the authentication path by ensuring only necessary host-to-guest features are enabled and that administrative access to ESXi remains tightly controlled.
- Review and restrict any custom scripts or automation that rely on host-to-guest channels.
These steps close the authentication bypass and restore the intended trust boundary between host and guest.
If you can't patch immediately
Until the update can be applied, reduce risk with compensating controls that limit the attacker’s ability to reach or abuse the vulnerable module.
- Segment ESXi management networks so that only authorized administrators can obtain root-level access; treat any host compromise as critical.
- Disable or restrict non-essential host-to-guest features that rely on vgauth if operationally feasible.
- Increase monitoring of ESXi root activity, guest authentication failures, and unexpected host-to-guest traffic; alert on anomalies.
- Apply virtual patching or host-based controls that block unauthorized management operations where possible.
- Ensure strong multi-factor authentication and least-privilege practices for all ESXi administrative accounts.
These measures shrink the window of exposure while the permanent fix is prepared. Confirm any configuration changes against the vendor advisory so that legitimate management functions are not broken.
If your data may have been exposed
Although known ransomware use of this vulnerability is not documented, any actively exploited authentication-bypass issue can lead to unauthorized access and subsequent data exposure. If you suspect host-to-guest operations were abused, treat the affected guests as potentially compromised: isolate them, preserve forensic evidence, and rotate credentials that may have been accessible. As a quick check for broader exposure, you can run a free scan of your email addresses against known breach data sets to see whether related accounts appear in public dumps.
AICompiled with AI assistance from public sources and published under our editorial standards.