Broadcom has patched an actively exploited vCenter authentication bypass, but the advisory doesn't list a public fix for 7.0. What should teams prioritize, and what are the options if an upgrade isn't immediate?
What are people doing about the vCenter authentication bypass, especially on 7.0?
Answers
Patch first where you can. The advisory lists fixes in 8.0 U3m, 9.0.2.0200 and 9.1.1.0200. For 7.0, it says customers with an extended support contract should contact Broadcom Support.
That still leaves the question of whether the system was compromised before the update. The reported activity dates back to early September, so a clean patch status today doesn't answer that.
Reply to this answer
Don't stop at updating the appliance. Check for unexpected local or SSO administrator accounts, SSH being enabled through the appliance management API and then disabled shortly afterward, and new root SSH keys on ESXi hosts. Also review connections to ports 2012 and 5480 from systems that shouldn't be talking to vCenter.
The reported tool copied the directory database, and another utility used a stolen SAML signing key to forge tokens that bypass MFA. If you find evidence of compromise, investigate replacing the signing certificate and rotating credentials the appliance could read. Bring in your incident response team rather than treating it as a routine patch.
Reply to this answer
For a 7.0 system that can't be upgraded immediately, I'd restrict management access as tightly as possible while working out the support or upgrade path. Keep it off the public internet and away from the ordinary LAN. Allow only the necessary management hosts or networks through the firewall.
That's risk reduction, not a fix. The reported attacker had already entered the network through another appliance, so an internal-only vCenter can still be reachable after a foothold.
Morlavi+7x:
A VPN or tightly restricted access proxy can help control remote administration, but it doesn't replace patching or checking for an existing compromise.
Reply to this answer
If 7.0 support and upgrades are becoming a recurring headache, this is also a reasonable time to evaluate other virtualization platforms. Hyper-V and Proxmox are options to assess, but don't assume either is a drop-in replacement for every vCenter setup. That's a longer project, not an immediate response to this vulnerability.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_h58+briskelo.7:
The reported activity also reached a vCenter that had already been patched for an earlier July vulnerability. That earlier fix shouldn't be taken as evidence that this one was blocked.