CVE-2025-43911
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 Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to arbitrary command execution. Exploitation may allow privilege escalation to root.
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 confidenceOS command injection vulnerability in Dell PowerProtect Data Domain systems running DD OS. A high-privileged local attacker can execute arbitrary OS commands, potentially escalating to root privileges. The vulnerability affects multiple Feature Release and LTS versions across a wide range.
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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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.
-
Identify the system as a Dell Data Domain applianceRun the command 'system show' or 'hostname' on the DD OS CLI to confirm the device is a Dell PowerProtect Data Domain system.Affected if The system is not a Dell Data Domain appliance running DD OS.
-
Determine the DD OS versionExecute the command 'version' or 'system show version' on the DD OS CLI to retrieve the installed Data Domain operating system version.Affected if Unable to retrieve the DD OS version from the system.
-
Compare the installed version against the affected rangesCompare the retrieved DD OS version to the following vulnerable ranges: 7.7.1.0 through 7.10.1.69, 7.13.1.0 through 7.13.1.39, 8.3.0.0 through 8.3.0.15, and 8.3.1.0 through 8.3.1.9. Check if the version falls within any of these ranges.Affected if The installed version is greater than or equal to 7.7.1.0 and less than 7.10.1.70, OR greater than or equal to 7.13.1.0 and less than 7.13.1.40, OR greater than or equal to 8.3.0.0 and less than or equal to 8.3.0.15, OR greater than or equal to 8.3.1.0 and less than 8.3.1.10.
-
Verify presence of high-privileged local accountsCheck if local user accounts with administrative privileges exist on the system using 'user' or 'show users' commands in DD OS CLI. This vulnerability requires a high-privileged local attacker to exploit the command injection.Affected if Local high-privileged accounts exist on the system.
The system is affected if it is a Dell PowerProtect Data Domain running a DD OS version within the specified vulnerable ranges and has local high-privileged user accounts.
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 patches for the affected DD OS versions (7.7.1.0-8.3.0.15, 8.3.1.0, 7.13.1.0-7.13.1.30, 7.10.1.0-7.10.1.60). Limit local/physical access to affected systems as a compensating control until patching is complete.
DD OS 7.10.1.70, 7.13.1.40, 8.3.0.16, or 8.3.1.10 (depending on which release branch you are on)
- 1. Identify the current Data Domain Operating System (DD OS) version running on the affected system using the 'ddos' CLI or admin console.
- 2. Based on the current version, determine the appropriate upgrade path to a fixed release:
- - For 7.7.x - 7.10.0.x: Upgrade to 7.10.1.70 or later
- - For 7.10.1.x (< 7.10.1.70): Upgrade to 7.10.1.70 or later
- - For 7.13.1.x (< 7.13.1.40): Upgrade to 7.13.1.40 or later
- - For 8.3.0.x (< 8.3.0.16): Upgrade to 8.3.0.16 or later
- - For 8.3.1.x (< 8.3.1.10): Upgrade to 8.3.1.10 or later
- 3. Download the appropriate DD OS upgrade package from Dell Support (support.dell.com) - ensure the package matches your Data Domain model.
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-43911 — 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-43911 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