INFO:
I'll pull up the advisory and check what Tenable has for it, then lay out the scan setup.
Good — there's a plugin. Let me check its details (type, dependencies, settings needed).
Yes, you can. Tenable already has a check for this advisory, so a Nessus scan before and after the update is a good way to show the fix worked. There's one catch: Nessus checks the version number vCenter reports. It doesn't actually try the attack.
What Nessus has for this advisory
- Plugin 383421 checks for the critical vCenter bug. It's a "Remote" plugin, published 11/19/2026, rated Critical. A plugin is a small test script that Nessus runs; "remote" means it works over the network without logging into the server.
- How it decides: Nessus doesn't test the flaw itself. It relies only on the version number vCenter reports about itself. That makes it safe to run against a production vCenter. It also means the "after" scan proves the version changed, not that the server is clean.
- Versions it flags: vCenter 7.0.x, 8.0 before 8.0 Update 3m, 9.0.x before 9.0.2.0200, and 9.1.x before 9.1.1.0200. If you're on vSphere 8, your target version is 8.0 U3m.
- Not covered yet: the SDDC Manager and VMware Tools for Windows bugs. On 11/19, Tenable's plugin pipeline listed VMSA-2026-0009 with all five CVEs as status "development". Right now this scan covers the vCenter bug only.
How to set up the scan
-
Update your plugins first. Plugin 383421 only exists in plugin feeds dated 11/19/2026 or later. In the web UI, go to Settings → Software Update → Update Now. On a Linux scanner, run
/opt/nessus/sbin/nessuscli update --plugins-only. Then search for plugin ID 383421 to make sure it's there. -
Create the scan. Go to New Scan → Advanced Scan. Name it something like "vCenter VMSA-2026-0009 check". Put only the vCenter's IP or hostname in Targets.
-
Choose which plugins to run (simple option). Leave all plugins on. Scanning one appliance is quick, and you can filter the results by plugin ID afterward. This avoids the most common beginner mistake: switching off the plugin that finds vCenter in the first place.
-
Choose which plugins to run (targeted option). If your team needs a narrow scan, enable these two:
- 63061 "VMware vCenter Detect": finds vCenter and reads its version.
- 383421: the advisory check.
Plugin 383421 needs the KB item "installed_sw/VMware vCenter Server" before it runs. That item is a note Nessus writes to itself during the scan, and the detect plugin is what writes it. Without 63061, the scan comes back empty and looks like a pass.
-
Check the ports. The default port scan is fine. Just make sure 443 is included, because that's where Nessus reads vCenter's version.
-
Credentials are optional. This check works without logging in. Leave "Safe checks" on (it is by default).
-
Run the "before" scan. You should see plugin 383421 marked Critical, with the installed version next to the fixed version. Export it as PDF or CSV to keep as evidence.
-
Patch vCenter. Afterward, confirm the new version in the appliance admin page at
https://<vcenter>:5480. -
Run the "after" scan. Relaunch the same scan so both runs sit in one scan history. The finding should be gone.
Check one more thing after the scan
A missing finding isn't proof by itself. If vCenter's services were still restarting, or port 443 was blocked, Nessus couldn't read the version at all. Plugin 383421 would then quietly not report. Open the result for plugin 63061 and confirm it shows the new version. You have a solid before/after record only when both are true: 63061 shows the new version, and 383421 is gone.
The scan can't tell you whether you were already attacked
This bug was used in real attacks before the patch came out. Broadcom fixed a critical vCenter authentication bypass that Chinese-linked hackers have exploited in zero-day attacks since September 2026. Patching closes the hole but doesn't undo anything an attacker already did. Do a few manual checks alongside the scans:
- Look in vCenter SSO for administrator accounts nobody created, and check the VAMI logs (the appliance admin page logs) for SSH being turned on and then off.
- Broadcom lists no workaround, so keep vCenter off the internet and allow port 2012 only from trusted management machines.
- If you suspect a compromise, rotate the vCenter STS signing certificate (the certificate vCenter uses to sign login tokens) and all SSO credentials. Patching alone doesn't remove forged SAML login tokens.
Comments
Post a Comment