Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Unsafe deserialization in Dell ControlVault3 cvhDecapsulateCmd

IdentifiersCVE-2025-24919CWE-502· Deserialization of Untrusted Data

CVE-2025-24919 is an unsafe deserialization vulnerability in Dell ControlVault3 prior to 5.15.10.14 and ControlVault3 Plus prior to 6.2.26.36. The flaw exists in the host-side cvhDecapsulateCmd functionality used by ControlVault’s Windows APIs to process firmware-defined response data. A specially crafted ControlVault response to a command can be deserialized unsafely by bcmbipdll.dll, leading to memory corruption; the supporting research specifically states this host-side decapsulation path can cause a stack overflow in host processes. The issue is exploitable when an attacker can cause the host to consume a malicious response from compromised or attacker-controlled ControlVault firmware.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in arbitrary code execution in the affected host process consuming the malicious ControlVault response. Because the surrounding ControlVault ecosystem includes high-privilege Windows services and biometric paths, exploitation may enable compromise of privileged Windows components and can be used as part of a chain to obtain SYSTEM privileges on the host. In the broader ReVault context, this also supports persistence and post-compromise operations when paired with malicious firmware on the Unified Security Hub.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by disabling unused ControlVault-related functionality and services, especially where fingerprint, smart card, or NFC features are not required. Monitor for abnormal loading of bcmbipdll.dll, unexpected access to the ControlVault device interface, and crashes in related services such as WinBioSvc, bcmHostStorageService, bcmHostControlService, or bcmUshUpgradeService. In higher-risk environments, consider disabling fingerprint login and enabling chassis intrusion detection and Windows Enhanced Sign-in Security where supported.

Remediation

Patch, then assume compromise.

Upgrade Dell ControlVault3 to version 5.15.10.14 or later and ControlVault3 Plus to version 6.2.26.36 or later. Apply Dell/Broadcom-provided firmware and software updates through Dell releases or Windows Update where available. Ensure both the ControlVault firmware and associated Windows API components are updated, since the vulnerable logic is in the host-side API processing path.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity9

Community discussion across Reddit, Mastodon, and other social sources.