Is itCheck something

No. CVE-2020-3952

A VMware vCenter Server bug is being used in attacks

Being used now

Yes. Attackers are using this right now.

What to do

Apply the vendor's update. If there is none, stop using it or cut it off from the internet.

Confirmed in attacks
Nov 3, 2021
Product
VMware vCenter Server
Attack likelihood, next 30 days
90%

Attack likelihood is EPSS, a daily estimate from FIRST.org of how likely this bug is to be used in attacks in the next 30 days.

The official description

VMware vCenter Server contains an information disclosure vulnerability in the VMware Directory Service (vmdir) when the Platform Services Controller (PSC) does not correctly implement access controls. Successful exploitation allows an attacker with network access to port 389 to extract sensitive information.

Required action: Apply updates per vendor instructions.

For your tech helper

A read-only checklist for whoever helps you with your computer, or an AI assistant. Paste it into Claude, ChatGPT or a coding agent; it only looks and changes nothing.

Read-only check, change nothing, send nothing anywhere.
Is VMware vCenter Server (CVE-2020-3952) installed or running on this machine or in this project?
1. Find every copy and its version (apps, packages, containers, lockfiles).
2. Compare each version against the vendor's fixed version for CVE-2020-3952. Quote the vendor page you used.
3. Report a table: where, version, fixed version, status (exposed / fixed / not installed / unsure).
4. List the exact update steps, but do not run them.

Sources