Who is affected
Broadcom VMware vCenter deployments are affected by an authentication bypass in the VMware Directory Service. The vulnerability allows an unauthenticated attacker with network access to bypass authentication and gain unauthorised access to the system. The record does not specify which versions of vCenter are vulnerable, nor does it detail which deployment architectures (standalone, linked mode, cloud-hosted) carry the highest risk.
How to check whether this touches you
- Inventory your infrastructure for any VMware vCenter instances, including those in development, staging and production environments.
- Establish whether each vCenter instance is reachable from an untrusted network: check firewall rules, network segmentation, and whether the Directory Service ports (typically 389, 636) are exposed to the internet or to subnets you do not control.
- Retrieve the running vCenter version from the administrative interface or via API; note that version alone is not conclusive evidence of vulnerability, as backported patches may have been applied to older releases.
- If vCenter is behind a load balancer or reverse proxy, confirm the proxy configuration does not inadvertently bypass authentication checks.
What to do
- As a first step, reduce reachability: restrict network access to vCenter Directory Service ports to only the IP ranges and systems that require it, using firewall rules or network policies.
- Consult Broadcom's vendor guidance for the specific patch or mitigation applicable to your vCenter version; apply patches in accordance with CISA BOD 26-04 risk-based patching timelines.
- If immediate patching is not possible, monitor Directory Service logs (typically found in
/var/log/vmware/sso/on the vCenter appliance) for failed authentication attempts, unusual bind requests, or access from unexpected sources. - Document the exposure window: note when this record was added to the CISA Known Exploited Vulnerabilities catalog and cross-reference your logs from that date backwards.
- If vCenter is internet-facing or if you cannot apply vendor mitigations, escalate to your change management and risk teams; the record advises that discontinuation may be necessary if mitigations are unavailable.
If you find you were exposed
Exploitation of authentication bypasses typically precedes public disclosure, so search your Directory Service logs, vCenter access logs and SSO audit logs from several weeks before the CISA KEV publication date. Focus on anomalous bind attempts, privileged account creation, or administrative sessions from unexpected source IPs. Log retention is often the limiting factor; if your logs do not cover the period of likely exploitation, escalate for guidance on forensic acquisition from backups or appliance snapshots.