dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-24311

HIGH · 8.4 CVSS v3.1 Published 2025-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An out-of-bounds read vulnerability exists in the cv_send_blockdata function of Dell ControlVault3 firmware. The vulnerability allows a specially crafted API call to read memory beyond intended boundaries, leading to sensitive information disclosure.

MitigationUpdate Dell ControlVault3 firmware to version 5.15.10.14 or later (ControlVault3) or 6.2.26.36 or later (ControlVault3 Plus) to patch the out-of-bounds read vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Dell ControlVault3 firmware variant
    Check system BIOS or use Dell SupportAssist/Command Configure to identify if the system has ControlVault3 or ControlVault3 Plus firmware installed. Look for 'ControlVault' in device manager or system information.
    Affected if The system does not have ControlVault3 or ControlVault3 Plus firmware present.
  2. Retrieve current firmware version
    Use Dell Command Configure, Dell Update Package, or BIOS information screen to obtain the installed ControlVault3 firmware version number. The version format is typically X.Y.Z.W.
    Affected if Unable to retrieve a firmware version number from the ControlVault3 device.
  3. Compare version to fixed releases
    Compare the installed version against 5.15.10.14 for ControlVault3 or 6.2.26.36 for ControlVault3 Plus. Determine if the installed version is lower than these thresholds.
    Affected if The installed ControlVault3 version is below 5.15.10.14, or ControlVault3 Plus version is below 6.2.26.36.
  4. Verify cv_send_blockdata API exposure
    Assess whether external or third-party applications have the ability to make API calls to the ControlVault3 device. This function is typically invoked through Dell security APIs or custom applications interfacing with the firmware.
    Affected if The cv_send_blockdata function is accessible to applications and the firmware version is vulnerable.

A system is affected if it runs Dell ControlVault3 firmware version below 5.15.10.14 or ControlVault3 Plus below 6.2.26.36, and the cv_send_blockdata API is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Dell ControlVault3 firmware to version 5.15.10.14 or later (ControlVault3) or 6.2.26.36 or later (ControlVault3 Plus) to patch the out-of-bounds read vulnerability.

Recommended fix High confidence

Dell ControlVault3: upgrade to version 5.15.10.14 or later; Dell ControlVault3 Plus: upgrade to version 6.2.26.36 or later

  1. Identify the current Dell ControlVault3 or ControlVault3 Plus firmware version installed on the system
  2. Navigate to Dell's support website (dell.com) and locate the appropriate BIOS/firmware update for the specific system model
  3. Download the firmware update package that includes ControlVault3 version 5.15.10.14 or later, or ControlVault3 Plus version 6.2.26.36 or later
  4. Follow Dell's recommended firmware update procedure, which typically involves running the firmware update utility with administrator privileges
  5. Restart the system as required to complete the firmware update process
  6. Verify the updated ControlVault firmware version matches the fixed release (5.15.10.14 for ControlVault3 or 6.2.26.36 for ControlVault3 Plus)
Caveat Firmware updates may require system restart and could have compatibility considerations with other security software; ensure backup of critical data before applying updates

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24311 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24311 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data