# CVE-2024-22264: VMware Avi Load Balancer updates address multiple vulnerabilities

> Administrators can escalate privileges to root on the host system, allowing full control over the load balancer infrastructure.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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:** 8 May 2024
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-pfmv-h3cf-mr72

## What is CVE-2024-22264?

CVE-2024-22264 is a high-severity vulnerability in VMware Avi Load Balancer, published on 8 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

VMware Avi Load Balancer contains a privilege escalation vulnerability. A malicious actor with admin privileges on VMware Avi Load Balancer can create, modify, execute and delete files as a root user on the host system.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2024-22264 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22264 is a high-severity vulnerability in VMware Avi Load Balancer, published on 8 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22264 in the wild and no public exploit code.

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

## Sources

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

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