# CVE-2019-5532: Information disclosure in vCenter Server

> Attackers with log access can view plaintext credentials for VMs deployed via OVF, potentially leading to unauthorized access.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4v8m-3x8w-h83j

## What is CVE-2019-5532?

CVE-2019-5532 is a high-severity vulnerability in Vmware Vcenter Server, published on 18 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

VMware vCenter Server (6.7.x prior to 6.7 U3, 6.5 prior to 6.5 U3 and 6.0 prior to 6.0 U3j) contains an information disclosure vulnerability due to the logging of credentials in plain-text for virtual machines deployed through OVF. A malicious user with access to the log files containing vCenter OVF-properties of a virtual machine deployed from an OVF may be able to view the credentials used to deploy the OVF (typically the root account of the virtual machine).

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2019-5532?

It affects 1 product.


Products: Vmware Vcenter Server.

## How do I fix CVE-2019-5532?

No fix has been published for CVE-2019-5532 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-5532 being exploited?

There is no known exploitation of CVE-2019-5532 in the wild and no public exploit code.

## 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-2020-3952](https://insights.sbomify.com/CVE-2020-3952/): VMware vCenter Server Information Disclosure (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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5532 and fix it if it is affected.

What it is: CVE-2019-5532 is a high-severity vulnerability in Vmware Vcenter Server, published on 18 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5532 in the wild and no public exploit code.

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-2019-5532/ (Markdown: https://insights.sbomify.com/CVE-2019-5532/index.md)
```

## Sources

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

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