CVE-2025-43913
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 · uneditedDell PowerProtect Data Domain with Data Domain Operating System (DD OS) of Feature Release versions 7.7.1.0 through 8.3.0.15, LTS2025 release version 8.3.1.0, LTS2024 release versions 7.13.1.0 through 7.13.1.30, LTS 2023 release versions 7.10.1.0 through 7.10.1.60, contain an Use of a Broken or Risky Cryptographic Algorithm vulnerability in the DDOS. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to information disclosure. The vulnerability could be leveraged by attackers to conduct phishing attacks that cause users to divulge sensitive information.
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 confidenceDell PowerProtect Data Domain appliances running DD OS contain a broken or risky cryptographic algorithm vulnerability that could allow unauthenticated remote attackers to disclose sensitive information. The vulnerability affects multiple feature release and LTS versions spanning from 7.7.1.0 through 8.3.1.0. Attackers could exploit this to conduct phishing attacks or intercept sensitive data due to weak cryptographic implementations.
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>= 7.7.1.0, < 7.10.1.70>= 7.13.1.0, < 7.13.1.40>= 8.3.0.0, <= 8.3.0.15>= 8.3.1.0, < 8.3.1.10CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Dell PowerProtect Data Domain applianceIdentify the hardware model or check system documentation to verify the device is a Dell PowerProtect Data Domain appliance running DD OS.Affected if Device is not a Dell PowerProtect Data Domain appliance - not affected.
-
Check DD OS versionAccess the Data Domain management interface or run 'ddos version' command via console/SSH to retrieve the installed DD OS version.Affected if Unable to determine version - cannot assess.
-
Compare version to affected rangesCompare the installed DD OS version against: 7.7.1.0 to 7.10.1.69, 7.13.1.0 to 7.13.1.39, 8.3.0.0 to 8.3.0.15, or 8.3.1.0 to 8.3.1.9. Ensure exact version matching (major.minor.maintenance.hotfix).Affected if Version falls within any of the listed ranges - potentially affected.
-
Check for cryptographic services in useReview enabled DD OS features and configurations related to encryption, SSL/TLS settings, or data-at-rest encryption. Examine system logs for any cryptographic warnings or errors.Affected if Cryptographic services are enabled and version is in affected range - likely affected.
The system is affected if it is a Dell PowerProtect Data Domain appliance running a DD OS version that falls within any of the four affected ranges: 7.7.1.0-7.10.1.69, 7.13.1.0-7.13.1.39, 8.3.0.0-8.3.0.15, or 8.3.1.0-8.3.1.9.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.10.1.707.13.1.408.3.1.10
Apply the vendor-supplied patch from Dell that addresses the cryptographic algorithm vulnerability. This is a firmware/OS update for the Data Domain appliance. Review Dell support advisory DSA-2025-099 for specific patch instructions.
DD OS 7.10.1.70 or later (for 7.x releases), DD OS 7.13.1.40 or later (for LTS2024), DD OS 8.3.1.10 or later (for 8.x releases)
- 1. Identify the current Data Domain Operating System (DD OS) version by running 'ddos-version' or checking the system management interface.
- 2. Determine which version range your current DD OS falls into (Feature Release, LTS2023, LTS2024, or LTS2025).
- 3. For Feature Release versions >= 7.7.1.0 and < 7.10.1.70: upgrade to DD OS version 7.10.1.70 or later.
- 4. For LTS2023 versions >= 7.10.1.0 and < 7.10.1.70: upgrade to DD OS version 7.10.1.70 or later.
- 5. For LTS2024 versions >= 7.13.1.0 and < 7.13.1.40: upgrade to DD OS version 7.13.1.40 or later.
- 6. For Feature Release versions >= 8.3.0.0 and <= 8.3.0.15: upgrade to DD OS version 8.3.1.10 or later.
- 7. For LTS2025 version 8.3.1.0: upgrade to DD OS version 8.3.1.10 or later.
- 8. Download the appropriate DD OS upgrade image from Dell Support (support.dell.com) and follow Dell's standard upgrade procedure.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43913 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-43913 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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