dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-24919

HIGH · 8.1 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
No privileges 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 deserialization of untrusted input vulnerability exists in the cvhDecapsulateCmd functionality of Dell ControlVault3 prior to 5.15.10.14 and ControlVault3 Plus prior to 6.2.26.36. A specially crafted ControlVault response to a command can lead to arbitrary code execution. An attacker can compromise a ControlVault firmware and have it craft a malicious response 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 deserialization vulnerability exists in the cvhDecapsulateCmd function of Dell ControlVault3 and ControlVault3 Plus firmware. An attacker who first compromises the ControlVault firmware can craft a malicious response to this function, leading to arbitrary code execution. The vulnerability stems from insecure handling of serialized data without proper validation.

MitigationUpdate Dell ControlVault3 firmware to version 5.15.10.14 or later, and ControlVault3 Plus to version 6.2.26.36 or later, as these contain the patched firmware that properly validates deserialized input.

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/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 ControlVault hardware
    Check system BIOS or hardware documentation for the presence of Dell ControlVault3 or ControlVault3 Plus security coprocessor
    Affected if System does not have ControlVault3 or ControlVault3 Plus hardware - not affected
  2. Check ControlVault3 firmware version
    Use Dell system diagnostics, Dell Command | Update utility, or access the firmware version through BIOS/security settings to retrieve the installed ControlVault3 firmware version
    Affected if Firmware version is below 5.15.10.14 (for ControlVault3) or version cannot be determined but hardware is present
  3. Check ControlVault3 Plus firmware version
    Use Dell system diagnostics, Dell Command | Update utility, or access the firmware version through BIOS/security settings to retrieve the installed ControlVault3 Plus firmware version
    Affected if Firmware version is below 6.2.26.36 (for ControlVault3 Plus) or version cannot be determined but hardware is present
  4. Verify cvhDecapsulateCmd function exposure
    This function is part of the ControlVault firmware command interface. If the firmware is older than the patched versions and the device is operational, the vulnerable function code is present
    Affected if Firmware version is unpatched and the ControlVault device is functional and accessible

A system is affected if it contains Dell ControlVault3 firmware before version 5.15.10.14 or ControlVault3 Plus firmware before version 6.2.26.36, as these versions contain the patch for the insecure deserialization in cvhDecapsulateCmd.

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, and ControlVault3 Plus to version 6.2.26.36 or later, as these contain the patched firmware that properly validates deserialized input.

Recommended fix High confidence

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

  1. Identify the ControlVault version on the affected Dell system using Dell Command | Update or Dell SupportAssist
  2. For ControlVault3 devices: Update ControlVault3 firmware to version 5.15.10.14 or later
  3. For ControlVault3 Plus devices: Update ControlVault3 Plus firmware to version 6.2.26.36 or later
  4. Download firmware updates from Dell's support site using the system Service Tag
  5. Apply firmware update via Dell Update Package (DUP) or BIOS update method
  6. Verify the firmware version has been successfully updated after reboot
Caveat Firmware updates carry inherent risk; ensure system is connected to power and do not interrupt the update process

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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