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

> Attackers with system log access can view plaintext cloud connection credentials in VMware Avi Load Balancer.

- **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:** 8 May 2024
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-p9h5-83v6-32fq

## What is CVE-2024-22266?

CVE-2024-22266 is a medium-severity vulnerability in VMware Avi Load Balancer, published on 8 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

VMware Avi Load Balancer contains an information disclosure vulnerability. A malicious actor with access to the system logs can view cloud connection credentials in plaintext.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2024-22266 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22266 is a medium-severity vulnerability in VMware Avi Load Balancer, published on 8 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22266 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-22266/ (Markdown: https://insights.sbomify.com/CVE-2024-22266/index.md)
```

## Sources

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

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