dbcve.org
Data Domain Operating SystemOperating system · Dell

CVE-2025-22475

HIGH · 7.5 CVSS v3.1 Published 2025-02-04
Fix available
A fix is available. Upgrade to 7.10.1.50 / 7.13.1.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 DD, versions prior to DDOS 8.3.0.0, 7.10.1.50, and 7.13.1.10 contains a use of a Cryptographic Primitive with a Risky Implementation vulnerability. A remote attacker could potentially exploit this vulnerability, leading to Information tampering.

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

Dell PowerProtect DD (Data Domain) OS contains a risky cryptographic implementation vulnerability. A remote attacker could exploit weak cryptographic primitives to tamper with information. The vulnerability affects DDOS versions prior to 8.3.0.0, 7.10.1.50, and 7.13.1.10.

MitigationUpgrade DDOS firmware to version 8.3.0.0, 7.10.1.50, 7.13.1.10 or later to address the cryptographic vulnerability.

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.10.1.0, < 7.10.1.50>= 7.13.1.0, < 7.13.1.10>= 7.14.0.0, < 8.3.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Determine the installed DDOS version
    Access the Data Domain CLI or management interface and run the command to display the system version (for example, using 'version' or 'system show version' in the DDOS CLI). Consult Dell documentation for the exact command if needed.
    Affected if The installed version falls within one of the following ranges: >= 7.10.1.0 and < 7.10.1.50, or >= 7.13.1.0 and < 7.13.1.10, or >= 7.14.0.0 and < 8.3.0.0
  2. Confirm the Data Domain model
    Verify the system is a Dell PowerProtect DD or Data Domain appliance running DDOS. Check the model number via CLI (for example, 'hardware show' or similar) or the physical system label.
    Affected if The system is a Dell Data Domain or PowerProtect DD appliance.
  3. Identify if remote management is enabled
    Review the network configuration to determine if remote management interfaces (such as the DDOS CLI over SSH, REST API, or management GUI) are accessible from network segments outside the trusted management zone.
    Affected if Remote management or API access is enabled and reachable from untrusted networks, providing a potential attack vector for exploiting the weak cryptographic primitives.

The environment is affected if the installed DDOS version is any release prior to 7.10.1.50, 7.13.1.10, or 8.3.0.0 within the supported version branches.

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.10.1.50 / 7.13.1.10 / 8.3.0.0 or later
Fixed in 7.10.1.507.13.1.108.3.0.0
Interim mitigation

Upgrade DDOS firmware to version 8.3.0.0, 7.10.1.50, 7.13.1.10 or later to address the cryptographic vulnerability.

Recommended fix High confidence

DDOS 8.3.0.0 (or latest available version)

  1. Verify current DDOS version by running the 'version' or 'system show version' command on the Data Domain CLI
  2. Review Dell PowerProtect DD upgrade guide and release notes for version 8.3.0.0 (or 7.10.1.50/7.13.1.10 based on your current branch)
  3. Ensure adequate storage capacity and system resources meet requirements for target version
  4. Schedule maintenance window as upgrades require system downtime
  5. Download the DDOS upgrade package from Dell Support (support.dell.com) using valid service contract
  6. Upload upgrade file to Data Domain using 'software upload' or equivalent command
  7. Verify upgrade package integrity using provided checksums
  8. Execute upgrade via 'software install' or equivalent command, following on-screen prompts
Caveat Review release notes for any configuration changes or deprecated features between your current version and 8.3.0.0; some legacy configurations may need adjustment

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

Fix this in Data Domain Operating System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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