# CVE-2021-22034: Information disclosure in VMware vRealize Operations Tenant App for VMware Cloud Director

> An information disclosure vulnerability in VMware vRealize Operations Tenant App allows attackers to read sensitive data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Oct 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-c76p-cr59-2v5j

## What is CVE-2021-22034?

CVE-2021-22034 is a high-severity vulnerability in VMware vRealize Operations Tenant App for VMware Cloud Director, published on 21 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Releases prior to VMware vRealize Operations Tenant App 8.6 contain an Information Disclosure Vulnerability.

## Which versions are affected by CVE-2021-22034?

It affects 1 product.


Products: Vmware Vrealize Operations Tenant.

## How do I fix CVE-2021-22034?

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

## Is CVE-2021-22034 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22034 and fix it if it is affected.

What it is: CVE-2021-22034 is a high-severity vulnerability in VMware vRealize Operations Tenant App for VMware Cloud Director, published on 21 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22034 in the wild and no public exploit code.

Affected product: VMware vRealize Operations Tenant App for VMware Cloud Director. 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-2021-22034/ (Markdown: https://insights.sbomify.com/CVE-2021-22034/index.md)
```

## Sources

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

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