dbcve.org
Data Domain Operating SystemOperating system · Dell

CVE-2025-36568

HIGH · 7.8 CVSS v3.1 Published 2026-04-17
Fix available
A fix is available. Upgrade to 7.13.1.60 / 8.3.1.30 or later.
See remediation →
80/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
Dell PowerProtect Data Domain BoostFS for client of Feature Release versions 7.7.1.0 through 8.5, LTS2025 release version 8.3.1.0 through 8.3.1.20, LTS2024 release versions 7.13.1.0 through 7.13.1.50, contain an insufficiently protected credentials vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to credential exposure. The attacker may be able to use the exposed credentials to access the system with privileges of the compromised account.

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

Dell PowerProtect Data Domain BoostFS for client contains an insufficiently protected credentials vulnerability in Feature Release versions 7.7.1.0 through 8.5, LTS2025 release 8.3.1.0 through 8.3.1.20, and LTS2024 release 7.13.1.0 through 7.13.1.50. A low-privileged local attacker can exploit this to access improperly protected credentials and gain unauthorized access to the system with the compromised account's privileges.

MitigationApply vendor-provided security patches for the affected PowerProtect Data Domain BoostFS versions. Rotate any credentials that may have been exposed and investigate the system for signs of compromise. Restrict local access to minimize attack surface until patches are applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Data Domain Operating SystemOperating system
Affected:>= 7.7.1.0, < 7.13.1.60>= 7.14.0.0, < 8.3.1.30>= 8.4.0.0, < 8.6.0.0

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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. Check Data Domain OS version
    Run 'ddboost version' or 'system show version' on the Data Domain CLI to retrieve the installed OS version
    Affected if The installed version is 7.7.1.0 through 7.13.1.59, or 7.14.0.0 through 8.3.1.29, or 8.4.0.0 through 8.5.x, or 8.6.0.0 (any version below 7.13.1.60, 8.3.1.30, or 8.6.0.0 depending on branch)
  2. Confirm BoostFS module is in use
    Check if BoostFS is configured by running 'ddboost fs show' or inspecting /ddboost/config for BoostFS-related configuration files
    Affected if BoostFS is enabled and the Data Domain OS version falls within the affected ranges
  3. Inspect credential storage files
    Examine /ddboost/credentials/ or /ddboost/etc/ directories for any world-readable or improperly permissioned credential files. Use 'ls -la' to check file permissions
    Affected if Any credential-related files exist with permissions allowing read access by non-root or non-privileged users (e.g., mode 644 or 666)
  4. Verify file ownership and permissions
    Run 'ls -la /ddboost/' and check if credential or config files are owned by non-privileged users or have overly permissive access rights
    Affected if Files in the BoostFS directories are owned by service accounts or have mode bits that permit unauthorized local users to read sensitive data

A user is affected if their Data Domain OS version is within 7.7.1.0 to 7.13.1.59, 7.14.0.0 to 8.3.1.29, or 8.4.0.0 to 8.5.x and BoostFS credential files have overly permissive permissions.

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
Upgrade available Upgrade to 7.13.1.60 / 8.3.1.30 / 8.6.0.0 or later
Fixed in 7.13.1.608.3.1.308.6.0.0
Interim mitigation

Apply vendor-provided security patches for the affected PowerProtect Data Domain BoostFS versions. Rotate any credentials that may have been exposed and investigate the system for signs of compromise. Restrict local access to minimize attack surface until patches are applied.

Recommended fix High confidence

Upgrade to Data Domain OS 8.6.0.0 or later (or to the latest available version for your LTS track)

  1. 1. Identify the current Data Domain Operating System version by running 'system show version' or checking the management console
  2. 2. If running a Feature Release version (7.7.1.0-8.5), upgrade to version 8.6.0.0 or later
  3. 3. If running LTS2025 (8.3.1.0-8.3.1.20), upgrade to version 8.3.1.30 or later
  4. 4. If running LTS2024 (7.13.1.0-7.13.1.50), upgrade to version 7.13.1.60 or later
  5. 5. Download the appropriate update from www.dell.com/support and follow Dell's standard upgrade procedures
  6. 6. After upgrade, verify the new version is running with 'system show version'
  7. 7. Review audit logs for any suspicious activity that may have occurred using exposed credentials
Caveat Standard OS upgrade downtime should be planned; verify backup jobs are not running during upgrade window

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

Fix this in Data Domain Operating System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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