# CVE-2024-22272: Privilege escalation in VMware Cloud Director

> An authenticated tenant administrator can accidentally disable their organization, causing a denial of service for active sessions within that scope.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jun 2024
- **Updated:** 2 Dec 2024
- **Also known as:** GHSA-289g-wh2w-9hg2

## What is CVE-2024-22272?

CVE-2024-22272 is a medium-severity vulnerability in VMware Cloud Director, published on 27 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

VMware Cloud Director contains an Improper Privilege Management vulnerability. 

An authenticated tenant administrator for a
 given organization within VMware Cloud Director may be able to 
accidentally disable their organization leading to a Denial of Service 
for active sessions within their own organization's scope.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-22272?


## How do I fix CVE-2024-22272?

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

## Is CVE-2024-22272 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22272 and fix it if it is affected.

What it is: CVE-2024-22272 is a medium-severity vulnerability in VMware Cloud Director, published on 27 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22272 in the wild and no public exploit code.

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

## Sources

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

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