CVE-2025-43907
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 a Path Traversal: '.../...//' vulnerability. A low privileged 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 · high confidenceA path traversal vulnerability exists in Dell PowerProtect Data Domain's DD OS where the sequence '.../...//' can be used to traverse outside the intended directory boundaries. A low-privileged remote attacker can exploit this to access sensitive files beyond the web root, leading to information exposure.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 the installed DD OS versionRun command 'ddos -version' or access the admin console to view the system version informationAffected if The installed version falls within >= 7.7.1.0 and < 7.10.1.70, OR >= 7.13.1.0 and < 7.13.1.40, OR >= 8.3.0.0 through 8.3.0.15, OR >= 8.3.1.0 and < 8.3.1.10
-
Verify the web management interface is enabledCheck if the HTTP/HTTPS management interface is active by attempting to access the web UI or reviewing system services with 'system show services'Affected if The web management interface is exposed and accessible to the attacker
-
Confirm low-privileged user accounts existReview user accounts via 'user list' or the admin console to identify non-administrative users with access to the web interfaceAffected if Low-privileged user accounts have access to the web management interface and can send HTTP requests
-
Test for path traversal if web UI is accessibleSend an HTTP request containing the sequence '.../...//' followed by a target path (such as '../../etc/passwd') to the web server endpointAffected if The server returns content from files outside the intended web root directory, confirming the vulnerability is exploitable
If the DD OS version is within any of the affected ranges AND the web management interface is accessible to low-privileged users, the environment is vulnerable to path traversal and information exposure.
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 for your specific DD OS version. Until patched, restrict network access to the management interface and limit low-privileged user permissions to the minimum required.
DD OS 7.10.1.70+ (LTS2023), 7.13.1.40+ (LTS2024), 8.3.1.10+ (LTS2025), or 8.3.0.16+ (Feature Release)
- 1. Identify the current Data Domain Operating System (DD OS) version by running 'ddos -version' or checking the system management interface
- 2. Determine which LTS branch your current version belongs to (LTS2023: 7.10.x, LTS2024: 7.13.x, LTS2025: 8.3.x, or Feature Release 7.7.x-8.3.0.x)
- 3. For LTS2023 (7.10.x): Upgrade to DD OS version 7.10.1.70 or later
- 4. For LTS2024 (7.13.x): Upgrade to DD OS version 7.13.1.40 or later
- 5. For LTS2025 (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 image from Dell Support (support.dell.com)
- 8. Follow standard DD OS upgrade procedures - typically via 'software' CLI command or the Data Domain System Manager
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43907 — 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-43907 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