CVE-2025-43934
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 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to Denial of service and Unauthorized access.
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 systems running DD OS versions 7.7.1.0 through 8.3.0.15, LTS2023 (7.10.1.0-7.10.1.60), LTS2024 (7.13.1.0-7.13.1.30), and LTS2025 (8.3.1.0) contain a path traversal vulnerability allowing a high-privileged local attacker to access files outside restricted directories, potentially causing denial of service or unauthorized system access.
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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed DD OS versionRun command `ddr version` or `system show version` on the Data Domain CLI to retrieve the operating system versionAffected if Version falls within 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
-
Confirm LTS branch versionIdentify if the system is on LTS2023 (7.10.x), LTS2024 (7.13.x), or LTS2025 (8.3.1.x) by examining the version output from the previous stepAffected if LTS2023 version is 7.10.1.0-7.10.1.60, LTS2024 is 7.13.1.0-7.13.1.30, or LTS2025 is 8.3.1.0 (any subversion)
-
Verify local high-privileged accounts existCheck for local administrator accounts using `user show` or similar command to list users with elevated privilegesAffected if Local users with administrative or root-level privileges are configured on the system
-
Inspect access to restricted directoriesReview system configuration for file access controls and any path traversal protection settings using `directory show` or filesystem access logsAffected if The system allows high-privileged local users to access directories outside their permitted scope
The system is affected if it runs DD OS version within the 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 AND has local high-privileged accounts that could exploit the path traversal vulnerability.
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 from Dell for the specific DD OS version in use; schedule maintenance window and test thoroughly in non-production environment before deploying to production systems.
Upgrade to 7.10.1.70+ (for 7.7.x-7.10.x trains), 7.13.1.40+ (for 7.13.x train), or 8.3.1.10+ (for 8.3.0.x/8.3.1.x trains)
- 1. Identify the current Data Domain Operating System (DD OS) version by running 'ddos version' or checking the system management interface
- 2. Determine the appropriate upgrade path based on current version: if on 7.7.x-7.10.x train, upgrade to 7.10.1.70 or later; if on 7.13.x train, upgrade to 7.13.1.40 or later; if on 8.3.0.x or 8.3.1.x train, upgrade to 8.3.1.10 or later
- 3. Download the appropriate DD OS upgrade package from Dell Support (www.dell.com/support) for the target fixed version
- 4. Review Dell Data Domain upgrade documentation and release notes for pre-upgrade prerequisites
- 5. Schedule a maintenance window and perform a complete system backup before upgrading
- 6. Upload the upgrade file to the Data Domain system using 'file upload' or the management interface
- 7. Execute the upgrade using 'system upgrade' command or through the GUI, following Dell's documented upgrade procedure
- 8. Verify the upgrade completed successfully and confirm the new version is running with 'ddos version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43934 — 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-43934 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