dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2025-36553

HIGH · 8.8 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 →
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
A buffer overflow vulnerability exists in the CvManager 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 memory corruption. 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 buffer overflow vulnerability in the CvManager component of Dell ControlVault3 and ControlVault3 Plus allows memory corruption via specially crafted ControlVault API calls. The vulnerability affects versions prior to 5.15.14.19 (ControlVault3) and 6.2.36.47 (ControlVault3 Plus).

MitigationApply Dell firmware updates to ControlVault3 (version 5.15.14.19 or later) or ControlVault3 Plus (version 6.2.36.47 or later) to remediate the vulnerability.

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 if Dell ControlVault3 or ControlVault3 Plus is installed
    Open Windows Programs and Features (appwiz.cpl) and look for entries named 'ControlVault3' or 'ControlVault3 Plus', or run 'wmic product get name,version' and filter for ControlVault entries
    Affected if Either ControlVault3 or ControlVault3 Plus software is present on the system
  2. Determine the installed ControlVault version
    Check the version of the installed ControlVault software via Programs and Features, or run 'wmic product where "name like '%ControlVault%'" get name,version' in an elevated command prompt
    Affected if The displayed version number is below 5.15.14.19 for ControlVault3 or below 6.2.36.47 for ControlVault3 Plus
  3. Verify the CvManager component is present
    CvManager is a core component of the ControlVault software; its presence is implied when the ControlVault3 or ControlVault3 Plus software is installed
    Affected if The ControlVault3 or ControlVault3 Plus software is installed and the CvManager component is active (which is the default when the software runs)
  4. Confirm the vulnerability trigger condition
    The vulnerability is triggered through specially crafted ControlVault API calls to the CvManager component; verify if applications or tools that interface with ControlVault APIs are in use
    Affected if Applications or scripts that make ControlVault API calls are running on the affected version

A user is affected if Dell ControlVault3 version is below 5.15.14.19 or ControlVault3 Plus version is below 6.2.36.47, and the CvManager component is active.

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 to ControlVault3 (version 5.15.14.19 or later) or ControlVault3 Plus (version 6.2.36.47 or later) to remediate the vulnerability.

Recommended fix Moderate confidence

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

  1. Identify the current ControlVault3 or ControlVault3 Plus firmware version using Dell Command Configure or BIOS information
  2. Download the appropriate firmware update from Dell's support website (support.dell.com) for your specific model
  3. Apply the firmware update using Dell Command Update, Dell Update Package (DUP), or through BIOS update process as documented by Dell
  4. Restart the system if required by the update process
  5. Verify the firmware has been updated to version 5.15.14.19 (ControlVault3) or 6.2.36.47 (ControlVault3 Plus) or later
Caveat Firmware updates may require system restart and should be tested in controlled environment before production deployment

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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