# CVE-2025-24311: Dell ControlVault3/ControlVault3 Plus cv_send_blockdata out-of-bounds read vulnerability

> An attacker can trigger an out-of-bounds read in Dell ControlVault firmware via a crafted API call, leading to information disclosure.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-5v6x-pfc7-q9g6

## What is CVE-2025-24311?

CVE-2025-24311 is a high-severity vulnerability in Broadcom BCM5820X, published on 13 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An out-of-bounds read vulnerability exists in the cv_send_blockdata 
functionality of Dell ControlVault3 prior to 5.15.10.14 and Dell ControlVault3 Plus prior to 6.2.26.36. A specially crafted 
ControlVault API call can lead to an information leak. An attacker can 
issue an API call to trigger this vulnerability.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-24311?


## How do I fix CVE-2025-24311?

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

## Is CVE-2025-24311 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24311 and fix it if it is affected.

What it is: CVE-2025-24311 is a high-severity vulnerability in Broadcom BCM5820X, published on 13 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24311 in the wild and no public exploit code.

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

## Sources

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

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