cyberplace.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Cybersecurity, fandom, video games, technology, dog photos and most importantly, you.

Server stats:

955
active users

3 different VMware zero days, under active exploitation by ransomware group

CVE-2025-22224, CVE-2025-22225, CVE-2025-22226

VMware ESXi
VMware Workstation Pro / Player (Workstation)
VMware Fusion
VMware Cloud Foundation
VMware Telco Cloud Platform

(Exploitation actually ESXi)

support.broadcom.com/web/ecx/s

Support PortalSupport Content Notification - Support Portal - Broadcom support portal

Unclear if related to this post from a few weeks ago.

You may want to escalate patching this as it allows virtual machine to hypervisor escape - e.g. from some dumb VM to the whole VMware private cloud estate.

VMware have set the Attack Vector to Local, which brings down the CVSS score - but you don't need to be locally at a VM to do the attack, you can do it over the internet if you have access to any VM.

If you change it to Network, you get 10

Kevin Beaumont

VMware ESXi vulns added to CISA KEV. HT @cisakevtracker

Good catch by @TomSellers - although VMware doesn't list ESXi 6.7 as vulnerable, it is - they've published a patch for it: techdocs.broadcom.com/us/en/vm

I think what's happening here is 6.7 is under premium (paid) extended support where they publish patches for high severity vulns for $$

This also tends to indicate it applies to other unsupported versions. The forum post suggested that vuln worked on ESXi 5.x - no patch is available that far back.

I think this may be a big problem for many orgs.

Another good catch by @TomSellers - VMware's website advisory has less detail than their github for some reason.

Their github: github.com/vmware/vcf-security

According to their Github, additional VMware ESXi versions are impacted (e.g. 6.5, 6.7) and older versions are likely impacted but no patches available.

An in the wild exploit for RCE hypervisor escape across every supported (and unsupported) product like this is unprecedent.

GitHubvcf-security-and-compliance-guidelines/security-advisories/vmsa-2025-0004 at main · vmware/vcf-security-and-compliance-guidelinesSecurity, compliance, and operational resilience resources applicable to VMware Cloud Foundation and VMware vSphere. This repository is an official VMware repository managed by Broadcom staff. - vm...

Quick mspaint.exe diagram on this, calling it ESXicape

- Have access to something like a Windows 11 Virtual Desktop system in VMware, or a Linux box or some such?

- Use ESXicape, a chain of three zero days, to gain access to the ESXi Hypervisor.

- Use that to access every other VM, and be on the management network of VMware cluster

One you have this level of access, traditionally you'll see groups like ransomware actors steal files and wipe things.

Does anybody know anybody at VMware Security who could have a look at the knowledge base article please?

It's missing 6.5 and 6.7, which are definitely vulnerable and have patches available on Broadcom's site. They're also listed in the VMware Github advisory, but have been missed off the support site. It's causing people to not patch.

Both VMware and Microsoft have declined to comment about , when asked about number of victims and who has the exploit.

A new twist on - you need local admin rights to escape the VM to the hypervisor, right?

Slight issue - VMware Tools, installed inside VMs, allows local user to local admin privilege escalation on every VM due to vuln CVE-2025-22230

“A malicious actor with non-administrative privileges on a Windows guest VM may gain ability to perform certain high-privilege operations within that VM.”

Discovered by Positive Technologies, who US claim hack for Moscow.

support.broadcom.com/web/ecx/s

Support PortalSupport Content Notification - Support Portal - Broadcom support portal

@GossiTheDog

In the Github version of the Advisory FAQ they actually state that ALL unpatched versions are vulnerable though they indicate that they haven't tested most unsupported versions. Here are few snippets from the link below:

You are affected if you are running any version of VMware ESX, VMware vSphere, VMware Cloud Foundation, or VMware Telco Cloud Platform prior to the versions listed as “fixed” in the VMSA.

For a definitive list of affected versions, please refer to the VMSA directly. If there is any uncertainty about whether a system is affected, it should be presumed vulnerable, and immediate action should be taken.

Does this impact VMware vSphere 6.5 or 6.7?

Yes. A patch has been released for ESX 6.7 and is available via the Support Portal to all customers. ESX 6.5 customers should use the extended support process for access to ESX 6.5 patches.

Products that are past their End of General Support dates are not evaluated as part of security advisories, and are not listed in the official VMSA. Broadcom strongly encourages all customers using vSphere 6.5 and 6.7 to update to vSphere 8.

github.com/vmware/vcf-security

GitHubvcf-security-and-compliance-guidelines/security-advisories/vmsa-2025-0004 at main · vmware/vcf-security-and-compliance-guidelinesSecurity, compliance, and operational resilience resources applicable to VMware Cloud Foundation and VMware vSphere. This repository is an official VMware repository managed by Broadcom staff. - vm...

@GossiTheDog Wonderful news to read during evening.... *le sigh* time to plan patching with team.

@GossiTheDog Thanks Kevin. Gonna forward this to some people that I know use VMware.

@GossiTheDog This might be because 6.5 and 6.7 are not longer general supported.

@GossiTheDog Broadcom's press team don't even reply to requests for interviews or comment any more; no guarantee there *is* anyone left in the security team

@vmstan @GossiTheDog good to know; it would certainly help if Broadcom's press team gave some proof of life as well!

@GossiTheDog they kept it off on purpose. The GitHub page even says so. It's weird though and is very confusing for those who actually might have a legit reason to run 6.5 and 6.7.
--------------
Products that are past their End of General Support dates are not evaluated as part of security advisories, and are not listed in the official VMSA. Broadcom strongly encourages all customers using vSphere 6.5 and 6.7 to update to vSphere 8.

github.com/vmware/vcf-security

GitHubvcf-security-and-compliance-guidelines/security-advisories/vmsa-2025-0004 at main · vmware/vcf-security-and-compliance-guidelinesSecurity, compliance, and operational resilience resources applicable to VMware Cloud Foundation and VMware vSphere. This repository is an official VMware repository managed by Broadcom staff. - vm...

@GossiTheDog thereby confirming it’s not going to be a good time for many

@GossiTheDog also one way around it is to migrate to OpenShift virtualization using easy migration tools 😀

@GossiTheDog can't say the first thing I would do would be loop legal in when making a change or a commit to a code repository 😆 i mean it would for me in this instance but it would be notifying them what i published unless i was instructed otherwise

@GossiTheDog @TomSellers didn’t 5.5 already have an unfixed escape in it?