# CVE-2022-22953: Information disclosure in VMware HCX

> A malicious actor with network access to the VMware HCX appliance can gain access to sensitive information.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 16 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rf24-8f9r-c453

## What is CVE-2022-22953?

CVE-2022-22953 is a medium-severity vulnerability in VMware HCX, published on 16 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

VMware HCX update addresses an information disclosure vulnerability. A malicious actor with network user access to the VMware HCX appliance may be able to gain access to sensitive information.

## Which versions are affected by CVE-2022-22953?

It affects 1 product.


Products: Vmware Vmware Hcx.

## How do I fix CVE-2022-22953?

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

## Is CVE-2022-22953 being exploited?

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

## Other vulnerabilities in VMware HCX

- [CVE-2024-38814](https://insights.sbomify.com/CVE-2024-38814/): SQL injection in VMware HCX (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22953 and fix it if it is affected.

What it is: CVE-2022-22953 is a medium-severity vulnerability in VMware HCX, published on 16 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22953 in the wild and no public exploit code.

Affected product: VMware HCX. 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-2022-22953/ (Markdown: https://insights.sbomify.com/CVE-2022-22953/index.md)
```

## Sources

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

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