Skip to main content

Nessus Scan - vCenter

 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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. Check the ports. The default port scan is fine. Just make sure 443 is included, because that's where Nessus reads vCenter's version.

  6. Credentials are optional. This check works without logging in. Leave "Safe checks" on (it is by default).

  7. 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.

  8. Patch vCenter. Afterward, confirm the new version in the appliance admin page at https://<vcenter>:5480.

  9. 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

Popular posts from this blog

Nov 17

 INFO: Only one package is missing, and it's my mistake. The command I gave you to check installed packages (in the short runbook) left out python3-unbound . So I wrongly told you no server had it. In fact every B server has python3-unbound , and it must be the same version as unbound-libs . The good news: that's the only problem. Kernel, vim, libtiff, rhc, LVM and GRUB all passed on every server. Fix: Download one more file from Red Hat (RHSA-2026:70754, RHEL 8 x86_64): python3-unbound-1.16.2-5.14.el8_10.4.x86_64.rpm Copy it to the B master: scp python3-unbound-1.16.2-5.14.el8_10.4.x86_64.rpm root@<rbb-ref-b-ansible>:/root/releases/2026.11/extra-rpms/ Step 2 again: answer y to "Use the existing folder" answer y to "Copy them into the repo?" answer y to the commands and to "Carry on" os-patch already points at rhel-8-10-nov2026 , so nothing changes there. Step 3 again. Every B server except vlim06 should show OK . v...

New Command 3

 INFO: These results are almost identical to the last run, which tells us the servers were still checking against an old copy of the repo list. Two things caused that. The B master is still running the old script. The message reads "dnf reports a conflict. Run: dnf update --assumeno", which is the 1.4 wording. Version 1.4.1 would also print dnf: lines underneath. The servers reused yesterday's repo list. When dnf reads a repo, it keeps a copy of the package list and reuses it for up to 48 hours. So the B servers checked against the list from before you added the 8 AppStream RPMs, and couldn't see them. That's why vlim03 still asks for perl and gcc. I've fixed the second one in the script: version 1.4.2 makes the dry run read the repo fresh every time. I've attached the script, the README (Word and PDF) and the pseudocode, all updated. Next steps: Copy os_patch_wizard.sh v1.4.2 to rbb-ref-b-ansible , replacing the old one. Check it with: grep...

New A Run

 INFO: You're in good shape at 5.8 GB free. The tar file can go straight from where it is. dbv6admin can already read /var/www/html/rbb-rhel8-repo-20261117.tar.gz , so it doesn't need copying to /tmp on B first. Only extra-rpms (160 MB) has to go through /tmp , because dbv6admin can't get into /root . On B, as root 1. Put extra-rpms where dbv6admin can reach it, and take the tar file's fingerprint cp -r /root/releases/2026.11/extra-rpms /tmp/ chown -R dbv6admin:dbv6admin /tmp/extra-rpms cp /root/os_patch_wizard_1.5.2.sh /tmp/ chown dbv6admin:dbv6admin /tmp/os_patch_wizard_1.5.2.sh sha256sum /var/www/html/rbb-rhel8-repo-20261117.tar.gz exit Write down the code sha256sum prints. You'll compare it on A. Skip the two wizard lines if A already has 1.5.2. To check, run grep SCRIPT_VERSION= /root/os_patch_wizard*.sh on A. On B, as dbv6admin 2. Send everything to A's /tmp scp /var/www/html/rbb-rhel8-repo-20261117.tar.gz dbv6admin@<A-master>:/tmp/ scp -r /tmp/...