dbcve.org
Use of Uninitialized ResourceWeakness · CWE-908

CVE-2025-31361

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 privilege escalation vulnerability exists in the ControlVault WBDI Driver WBIO_USH_ADD_RECORD functionality of Dell ControlVault3 prior to 5.15.14.19 and Dell ControlVault3 Plus prior to 6.2.36.47. A specially crafted WinBioControlUnit call can lead to privilege escalation. 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 privilege escalation vulnerability exists in Dell ControlVault WBDI Driver's WBIO_USH_ADD_RECORD functionality. The flaw allows an attacker to use a specially crafted WinBioControlUnit API call to escalate privileges, likely by bypassing access controls in the kernel-mode biometric driver.

MitigationUpdate Dell ControlVault3 to version 5.15.14.19 or later, and Dell ControlVault3 Plus to version 6.2.36.47 or later. Apply the Dell security update through Dell Update or Dell Command | Update 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. Verify Dell ControlVault WBDI Driver presence
    Open Device Manager, expand 'Biometric devices', and look for 'Dell ControlVault WBDI' or run 'driverquery /v | findstr -i controlvault' in Command Prompt
    Affected if The driver is present in Device Manager or driverquery output
  2. Find the installed driver version
    Right-click the Dell ControlVault WBDI device in Device Manager, go to Driver tab, and note the Driver Version. Alternatively, run 'wmic path win32_pnpsigneddriver where "DeviceName like '%ControlVault%'" get DeviceName,DriverVersion'
    Affected if Driver is installed but version cannot be determined or is visible
  3. Compare against fixed version for ControlVault3
    If you have Dell ControlVault3 (non-Plus), compare your driver version to 5.15.14.19. Versions below this are affected
    Affected if Installed version is below 5.15.14.19 for ControlVault3
  4. Compare against fixed version for ControlVault3 Plus
    If you have Dell ControlVault3 Plus, compare your driver version to 6.2.36.47. Versions below this are affected
    Affected if Installed version is below 6.2.36.47 for ControlVault3 Plus
  5. Check if biometric service is active
    Open Services (services.msc), locate Windows Biometric Service, and check its Status. Also verify the driver is loaded via 'sc query winbio' or 'sc query WbioSvc'
    Affected if Biometric service is running and the driver version is below the fixed versions

You are affected if the Dell ControlVault WBDI Driver is installed and its version is below 5.15.14.19 (ControlVault3) or below 6.2.36.47 (ControlVault3 Plus), with the biometric service enabled.

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 to version 5.15.14.19 or later, and Dell ControlVault3 Plus to version 6.2.36.47 or later. Apply the Dell security update through Dell Update or Dell Command | Update tools.

Recommended fix High confidence

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

  1. Identify the Dell system model and determine if it uses Dell ControlVault3 or Dell ControlVault3 Plus
  2. Check the current version of the ControlVault WBDI Driver (WBIO) installed on the system
  3. For systems running Dell ControlVault3: upgrade the ControlVault driver to version 5.15.14.19 or later
  4. For systems running Dell ControlVault3 Plus: upgrade the ControlVault driver to version 6.2.36.47 or later
  5. Obtain the driver update from Dell's official support website or through Dell Update packages
  6. Apply the driver update following Dell's standard firmware/driver update procedures
  7. Verify the installed driver version matches the target fixed version
Caveat Driver/firmware updates may require system restart; ensure proper backup and downtime planning

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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