# CVE-2020-3952: VMware vCenter Server Information Disclosure

> Attackers can bypass access controls in VMware vCenter Server's vmdir component, potentially gaining unauthorized access to sensitive services.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-rqpw-v3g2-qccx

## What is CVE-2020-3952?

CVE-2020-3952 is a critical missing authorization vulnerability in Vmware Vcenter Server, published on 10 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Under certain conditions, vmdir that ships with VMware vCenter Server, as part of an embedded or external Platform Services Controller (PSC), does not correctly implement access controls.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2020-3952?

It affects 1 product.


Products: Vmware Vcenter Server.

## How do I fix CVE-2020-3952?

No fix has been published for CVE-2020-3952 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-3952 being exploited?

Yes. Attackers have exploited CVE-2020-3952 in the wild since at least 3 Nov 2021.

Public exploit code:

- Exploit for CVE-2020-3952 in vCenter 6.7 (github_poc): https://github.com/guardicore/vmware_vcenter_cve_2020_3952
- Vuln Check (github_poc): https://github.com/chronoloper/CVE-2020-3952
- Exploit for CVE-2020-3952 in vCenter 6.7 https://www.guardicore.com/2020/04/pwning-vmware-vcenter-cve-2020-3952/ (github_poc): https://github.com/Fa1c0n35/vmware_vcenter_cve_2020_3952
- VMWare vmdir missing access control exploit checker (github_poc): https://github.com/gelim/CVE-2020-3952
- VMware vCenter Server vmdir Authentication Bypass (metasploit)
- VMware vCenter Server vmdir Information Disclosure (metasploit)

## Other vulnerabilities in Vmware Vcenter Server

- [CVE-2026-59310](https://insights.sbomify.com/CVE-2026-59310/): Broadcom VMware vCenter Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2023-34048](https://insights.sbomify.com/CVE-2023-34048/): VMware vCenter Server Out-of-Bounds Write (critical 9.8, exploited in the wild)
- [CVE-2021-22017](https://insights.sbomify.com/CVE-2021-22017/): VMware vCenter Server Improper Access Control (medium 5.3, exploited in the wild)
- [CVE-2015-2342](https://insights.sbomify.com/CVE-2015-2342/): Code injection in n/a (critical 10.0)
- [CVE-2026-59309](https://insights.sbomify.com/CVE-2026-59309/): vCenter authentication-bypass vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-3952 and fix it if it is affected.

What it is: CVE-2020-3952 is a critical missing authorization vulnerability in Vmware Vcenter Server, published on 10 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-3952 in the wild since at least 3 Nov 2021.

Affected product: Vmware Vcenter Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-3952/ (Markdown: https://insights.sbomify.com/CVE-2020-3952/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-3952
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-3952
- OSV: https://osv.dev/vulnerability/CVE-2020-3952

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-3952/
Summaries are generated and may contain mistakes; the official description above is the record.