# CVE-2022-38650: Deserialization in n/a

> Remote attackers can execute arbitrary code on VMware Hyperic Server via insecure deserialization, affecting unsupported legacy software.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-j6cj-g4pc-56gc

## What is CVE-2022-38650?

CVE-2022-38650 is a critical unsafe deserialization vulnerability in n/a, published on 12 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote unauthenticated insecure deserialization vulnerability exists in VMware Hyperic Server 5.8.6. Exploitation of this vulnerability enables a malicious party to run arbitrary code or malware within Hyperic Server and the host operating system with the privileges of the Hyperic server process. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Vmware Hyperic Server.

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

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

## Is CVE-2022-38650 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-38651](https://insights.sbomify.com/CVE-2022-38651/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38650 is a critical unsafe deserialization vulnerability in n/a, published on 12 Nov 2022. 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-2022-38650 in the wild and no public exploit code.

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

## Sources

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

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