CVE-2025-43905
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 Argument Delimiters in a Command ('Argument Injection') vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Denial of service.
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 an argument injection vulnerability where improper neutralization of argument delimiters allows a low-privileged remote attacker to inject malicious arguments into system commands, potentially causing denial of service.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Identify installed DD OS versionRun 'ddos -v' or 'system show version' via admin CLI to retrieve the exact DD OS version numberAffected if The installed version falls within any of these ranges: 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
-
Check for exposed management interfacesVerify whether SSH (port 22), web UI (port 443), or other remote management protocols are accessible from untrusted networks. Use 'netstat -an | grep LISTEN' or review firewall rules.Affected if Remote management interfaces are open to untrusted networks and the DD OS version is in the affected list
-
Review enabled remote authentication methodsCheck 'adminaccess' configuration: run 'adminaccess show' in DD OS CLI to see enabled access methods and associated user privilegesAffected if Remote authentication is enabled for low-privilege users (non-admin accounts) and the system is running an affected version
-
Audit low-privilege user accountsList local user accounts with 'user list' and check for low-privilege accounts that have remote login capabilityAffected if Low-privilege users exist with remote access permissions on an affected DD OS version
-
Inspect command execution loggingReview DD OS audit logs for suspicious command patterns or unexpected arguments. Check 'logs show' for entries containing unusual delimiters or injected parameters.Affected if Log analysis reveals anomalous command executions with unexpected arguments, indicating potential exploitation attempts
A system is likely affected if it runs a DD OS version within the specified ranges AND has remote access enabled for low-privilege users.
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 for 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). Restrict remote access to only authorized personnel and monitor for anomalous command execution until patching is complete.
DD OS 8.3.1.10 (or later LTS/Feature release)
- Identify the current DD OS version running on the Data Domain system using the 'version' or 'system show version' command.
- Determine which release track the system is on (Feature Release, LTS2025, LTS2024, or LTS2023).
- For Feature Release and LTS2025: Upgrade to version 8.3.1.10 or later.
- For LTS2024: Upgrade to version 7.13.1.40 or later.
- For LTS2023: Upgrade to version 7.10.1.70 or later.
- Schedule the upgrade during a maintenance window as the system may require a reboot.
- After upgrade, verify the new version is running using 'version' command and confirm the vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43905 — 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-43905 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