dbcve.org
Use of Uninitialized ResourceWeakness · CWE-908

CVE-2025-31649

HIGH · 8.7 CVSS v3.1 Published 2025-11-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/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
A hard-coded password vulnerability exists in the ControlVault WBDI Driver functionality of Dell ControlVault3 prior to 5.15.14.19 and Dell ControlVault3 Plus prior to 6.2.36.47. A specially crafted ControlVault API call can lead to execute priviledged operation. 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 · moderate confidence

A hardcoded password vulnerability exists in the Dell ControlVault WBDI (Windows Biometric Device Interface) Driver for ControlVault3 (versions prior to 5.15.14.19) and ControlVault3 Plus (versions prior to 6.2.36.47). Attackers can exploit this by issuing specially crafted ControlVault API calls that leverage the hardcoded credentials to execute privileged operations on the system.

MitigationApply Dell firmware/driver updates: upgrade ControlVault3 to version 5.15.14.19 or later, and ControlVault3 Plus to version 6.2.36.47 or later. Verify the update through vendor-supplied installation verification tools.

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
Low

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

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 WBDI driver version
    Open Windows Device Manager, expand the Biometric devices category, locate the ControlVault WBDI device, view its Properties, and record the Driver Version shown
    Affected if The driver version displayed is earlier than 5.15.14.19 for ControlVault3, or earlier than 6.2.36.47 for ControlVault3 Plus
  2. Check if biometric driver is loaded
    In Windows Device Manager, verify that the ControlVault WBDI device shows as 'This device is working properly' and is not disabled or greyed out
    Affected if The driver is installed, enabled, and actively running on the system
  3. Determine ControlVault hardware type
    Check system BIOS information, Dell SupportAssist, or system documentation to identify whether the device uses ControlVault3 or ControlVault3 Plus hardware
    Affected if The system contains ControlVault3 or ControlVault3 Plus biometric hardware

If the ControlVault WBDI driver is loaded and its version falls below 5.15.14.19 (for ControlVault3) or below 6.2.36.47 (for ControlVault3 Plus), the environment is affected by this vulnerability.

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 Dell firmware/driver updates: upgrade ControlVault3 to version 5.15.14.19 or later, and ControlVault3 Plus to version 6.2.36.47 or later. Verify the update through vendor-supplied installation verification tools.

Recommended fix Moderate confidence

Dell ControlVault3: version 5.15.14.19 or later; Dell ControlVault3 Plus: version 6.2.36.47 or later

  1. Identify the current version of Dell ControlVault3 or ControlVault3 Plus driver installed on the system
  2. Navigate to Dell's support website (support.dell.com) and search for the latest ControlVault driver for your specific Dell system model
  3. Download the updated ControlVault driver version 5.15.14.19 or later for ControlVault3, or version 6.2.36.47 or later for ControlVault3 Plus
  4. Run the downloaded driver installer with administrative privileges
  5. Follow the on-screen installation prompts to complete the driver update
  6. Restart the system if prompted to complete the installation

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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