CVE-2025-43909
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 DD boost. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Information exposure.
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 confidenceDell PowerProtect Data Domain systems running DD OS contain a broken or risky cryptographic algorithm vulnerability in the DD Boost component. An unauthenticated remote attacker with network access could exploit this vulnerability to expose sensitive information due to the use of weak or improper cryptographic protections.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify DD OS versionLog into the Data Domain system via console or SSH and run the command to display the DD OS version (typically 'version' or 'ddos -version'). Compare the installed version to the affected ranges: 7.7.1.0 to <7.10.1.70, 7.13.1.0 to <7.13.1.40, 8.3.0.0 to 8.3.0.15, or 8.3.1.0 to <8.3.1.10.Affected if The installed version falls within any of the listed affected ranges.
-
Confirm DD Boost is enabledCheck the DD Boost configuration status on the Data Domain system. DD Boost is typically managed through the Data Domain Management Center (DDMC) or via CLI commands. Verify whether the DD Boost service or protocol is actively enabled on the system.Affected if DD Boost is enabled and running on the system.
-
Verify DD Boost network accessibilityDetermine if the DD Boost interface (typically port 2049 or configured DD Boost ports) is exposed to the network. Check network listen settings, firewall rules, or interface bindings to see if DD Boost accepts remote connections from untrusted networks.Affected if DD Boost is network-accessible from untrusted or external network segments.
You are affected if your DD OS version is within the specified ranges AND DD Boost is enabled and network-accessible to an unauthenticated remote attacker.
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 vendor-supplied patches or upgrade to a patched DD OS version beyond the listed affected releases. If immediate patching is not feasible, consider disabling DD Boost or restricting network access to the DD Boost interface as a compensating control.
Upgrade to DD OS 7.10.1.70+ (LTS2023), 7.13.1.40+ (LTS2024), 8.3.1.10+ (LTS2025), or 8.3.0.16+ (Feature Release) based on your current track
- 1. Identify the current Data Domain Operating System (DD OS) version by running 'ddr version' or checking the management console.
- 2. Determine which release track your current version belongs to (LTS2023, LTS2024, LTS2025, or Feature Release).
- 3. For LTS2023 releases (7.10.1.x): Upgrade to DD OS version 7.10.1.70 or later.
- 4. For LTS2024 releases (7.13.1.x): Upgrade to DD OS version 7.13.1.40 or later.
- 5. For LTS2025 releases (8.3.1.x): Upgrade to DD OS version 8.3.1.10 or later.
- 6. For Feature Release (8.3.0.x): Upgrade to DD OS version 8.3.0.16 or later.
- 7. Download the appropriate DD OS upgrade package from Dell Support (www.dell.com/support).
- 8. Follow Dell's standard DD OS upgrade procedure: upload the upgrade file, verify checksum, and execute the upgrade with 'system upgrade start' command.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43909 — 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-43909 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