dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2025-25050

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
An out-of-bounds write vulnerability exists in the cv_upgrade_sensor_firmware functionality of Dell ControlVault3 prior to 5.15.10.14 and Dell ControlVault 3 Plus prior to 6.2.26.36. A specially crafted ControlVault API call can lead to an out-of-bounds write. 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

An out-of-bounds write vulnerability exists in the cv_upgrade_sensor_firmware functionality of Dell ControlVault3 (prior to 5.15.10.14) and ControlVault 3 Plus (prior to 6.2.26.36). A specially crafted ControlVault API call can trigger memory corruption during the sensor firmware upgrade process, potentially leading to code execution or denial of service.

MitigationApply Dell firmware updates: upgrade ControlVault3 to version 5.15.10.14 or later, and ControlVault 3 Plus to version 6.2.26.36 or later. Restrict firmware upgrade API calls to authorized administrative functions only.

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 ControlVault model
    Open Device Manager, expand 'System devices', and look for 'Dell ControlVault' or 'Dell ControlVault 3 Plus' entry. Alternatively, run 'wmic path win32_computersystemproduct get name' or check Dell BIOS information (press F2 at boot).
    Affected if The system shows Dell ControlVault or ControlVault 3 Plus hardware
  2. Check ControlVault firmware version
    Use Dell Command | Update, or run the Dell Update Package (DUP) for ControlVault, or check via BIOS/UEFI (F2 at boot -> Device Configuration -> ControlVault). Compare the installed version against the affected thresholds: ControlVault3 < 5.15.10.14, ControlVault 3 Plus < 6.2.26.36.
    Affected if Firmware version is below 5.15.10.14 for ControlVault3 or below 6.2.26.36 for ControlVault 3 Plus
  3. Verify firmware upgrade API accessibility
    Check if the ControlVault firmware upgrade API (cv_upgrade_sensor_firmware) is exposed to non-administrative users. Review application or service configurations that interface with ControlVault, and audit user privileges accessing firmware upgrade interfaces.
    Affected if Firmware upgrade API calls are reachable from non-administrative or untrusted code contexts
  4. Audit ControlVault upgrade-related services
    Review running services or daemons that handle ControlVault firmware operations. Check for unusual or unauthorized processes invoking sensor firmware upgrade routines. Use 'wmic service list brief' or 'sc query' on Windows, or 'systemctl list-units' on Linux, to enumerate relevant services.
    Affected if Services handling firmware upgrades are running with excessive privileges or are accessible to low-privilege users

The system is affected if it contains Dell ControlVault3 with firmware before 5.15.10.14 or ControlVault 3 Plus before 6.2.26.36, AND the firmware upgrade API is accessible to callers who should not have that access.

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 updates: upgrade ControlVault3 to version 5.15.10.14 or later, and ControlVault 3 Plus to version 6.2.26.36 or later. Restrict firmware upgrade API calls to authorized administrative functions only.

Recommended fix High confidence

Dell ControlVault3: upgrade to 5.15.10.14 or later; Dell ControlVault 3 Plus: upgrade to 6.2.26.36 or later

  1. 1. Identify the current firmware version of Dell ControlVault3 or ControlVault 3 Plus installed on the affected system
  2. 2. Navigate to Dell's support website or use Dell Update utility to check for firmware updates
  3. 3. Download and apply Dell ControlVault3 firmware version 5.15.10.14 or later for ControlVault3 systems
  4. 4. Download and apply Dell ControlVault 3 Plus firmware version 6.2.26.36 or later for ControlVault 3 Plus systems
  5. 5. Reboot the system after applying the firmware update
  6. 6. Verify the firmware version has been successfully updated to the fixed release

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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