# CVE-2022-2664: Private Cloud Management Platform POST Request global_config_query improper authentication

> Attackers can bypass authentication on the global config query endpoint to access sensitive management data.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2022
- **Updated:** 14 Apr 2025
- **Also known as:** GHSA-m576-xv6p-w8w5

## What is CVE-2022-2664?

CVE-2022-2664 is a high-severity authentication bypass vulnerability in unspecified Private Cloud Management Platform, published on 5 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in Private Cloud Management Platform. Affected is an unknown function of the file /management/api/rcx_management/global_config_query of the component POST Request Handler. The manipulation leads to improper authentication. It is possible to launch the attack remotely. VDB-205614 is the identifier assigned to this vulnerability.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Private Cloud Management Platform Project Private Cloud Management Platform.

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

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

## Is CVE-2022-2664 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2664 is a high-severity authentication bypass vulnerability in unspecified Private Cloud Management Platform, published on 5 Aug 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-2664 in the wild and no public exploit code.

Affected product: unspecified Private Cloud Management Platform. 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-2664/ (Markdown: https://insights.sbomify.com/CVE-2022-2664/index.md)
```

## Sources

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

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