dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2025-24922

HIGH · 8.8 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 →
90/100
Remediation priority · Urgent
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
A stack-based buffer overflow vulnerability exists in the securebio_identify functionality of Dell ControlVault3 prior to 5.15.10.14 and Dell ControlVault3 Plus prior to 6.2.26.36. A specially crafted malicious cv_object can lead to a arbitrary code execution. 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

A stack-based buffer overflow exists in the securebio_identify function of Dell ControlVault3 and ControlVault3 Plus. An attacker can exploit this by issuing a specially crafted malicious cv_object through an API call, causing the buffer overflow and achieving arbitrary code execution.

MitigationApply the vendor-supplied firmware/driver updates: upgrade Dell ControlVault3 to version 5.15.10.14 or later, and ControlVault3 Plus to 6.2.26.36 or later. Until patching is possible, limit access to the vulnerable API and monitor for indicators of compromise.

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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 ControlVault3 hardware presence
    Check system hardware information (DMIDECODE, system information tools, or device manager) for Dell ControlVault3 or ControlVault3 Plus firmware devices. Look for 'ControlVault' entries in the system BIOS or firmware inventory.
    Affected if The system contains Dell ControlVault3 or ControlVault3 Plus hardware firmware.
  2. Retrieve current firmware version
    Use Dell firmware update tools (e.g., Dell Update Package, Dell Command | Configure, or BIOS setup) to query the installed ControlVault firmware version. Check the firmware revision listed for the security device.
    Affected if The installed firmware version is below 5.15.10.14 for ControlVault3 or below 6.2.26.36 for ControlVault3 Plus.
  3. Verify securebio API exposure
    Review system logs and API access controls to determine if the securebio_identify function API is exposed to untrusted callers. Check for any custom or third-party software that invokes the ControlVault bio identification API.
    Affected if The securebio_identify API is accessible to untrusted or external callers, or unusual API call patterns are logged.
  4. Inspect for indicators of compromise
    Review security event logs for any unexpected process activity, memory corruption indicators, or anomalies around firmware/driver interactions. Check for any unsigned code execution or unexpected DLL loading related to ControlVault components.
    Affected if Logs show suspicious API calls to securebio_identify, memory anomalies, or unexpected code execution patterns.

A system is affected if it has Dell ControlVault3 (version below 5.15.10.14) or ControlVault3 Plus (version below 6.2.26.36) firmware AND has the vulnerable API accessible for exploitation.

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

Apply the vendor-supplied firmware/driver updates: upgrade Dell ControlVault3 to version 5.15.10.14 or later, and ControlVault3 Plus to 6.2.26.36 or later. Until patching is possible, limit access to the vulnerable API and monitor for indicators of compromise.

Recommended fix High confidence

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

  1. Identify the Dell ControlVault3 device model in use (ControlVault3 or ControlVault3 Plus)
  2. Check the current firmware version installed on the device
  3. Download the firmware update from the Dell Support website (support.dell.com) using the device Service Tag
  4. Apply firmware version 5.15.10.14 or later for ControlVault3, or version 6.2.26.36 or later for ControlVault3 Plus
  5. Verify the firmware update was successfully applied by checking the updated version number
Caveat Firmware updates may require system downtime and should be tested in a non-production environment first; ensure the device has adequate battery power or is connected to AC power during the update process to prevent brickage

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24922 — 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-24922 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