CVE-2025-43890
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 DD OS allows high-privileged local attackers to execute arbitrary commands due to improper neutralization of special elements in OS commands, potentially achieving root privilege escalation.
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 installed DD OS versionRun 'ddr version' or access the Data Domain Management Console (DDMC) to view the system version under Administration > Hardware > System InformationAffected if The 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
-
Verify admin user access controlsReview /etc/passwd and /data/col/etc/adminusr file (or equivalent) for unauthorized high-privilege accounts created after the patch dates; check for unexpected entries in the admin groupAffected if Any unauthorized or unexpected accounts exist with root or admin privileges, or if multiple high-privileged users exist beyond the expected baseline
-
Audit recent command history for suspicious activityReview shell history files (e.g., /home/admin/.bash_history or /root/.bash_history) and system logs in /var/log/messages for unusual commands containing semicolons, pipes, backticks, or $() subshellsAffected if Commands contain OS injection patterns such as '; rm -rf', '| bash', '$(whoami)', '`id`', or other unexpected command chaining
-
Check for unexpected processes or network connectionsRun 'ps -ef' and 'netstat -anp' (or equivalent) to list running processes and listening ports for any unauthorized or suspicious executables spawned from web interfaces or management servicesAffected if Unexpected processes are running, especially those spawned by nginx, httpd, or other web services executing shell commands
-
Review DD OS system logs for injection attemptsExamine /data/col/var/log/audit/audit.log and /data/col/var/log/messages for entries containing 'sh:', 'bash:', or failed command execution errors near the time of suspicious activityAffected if Log entries show command injection attempts, particularly from the management interface or admin user sessions
Your environment is affected if the installed DD OS version matches any of the four vulnerable version ranges AND an attacker with high-privileged local access could exploit the command injection to gain root privileges.
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 Dell's patched versions as specified in the security advisory; until then, strictly limit local administrative access and monitor for anomalous command execution.
7.10.1.70+ (LTS2023), 7.13.1.40+ (LTS2024), 8.3.1.10+ (LTS2025/Feature Release)
- 1. Identify the current Data Domain Operating System (DD OS) version running on the affected system using the 'version' or 'system show version' command.
- 2. Determine the appropriate LTS (Long Term Support) branch for your deployment based on the official support lifecycle.
- 3. For systems running 7.10.1.x (LTS 2023): Upgrade to version 7.10.1.70 or later.
- 4. For systems running 7.13.1.x (LTS 2024): Upgrade to version 7.13.1.40 or later.
- 5. For systems running 8.3.0.x (Feature Release): Upgrade to version 8.3.1.10 or later.
- 6. For systems running 8.3.1.x (LTS 2025): Upgrade to version 8.3.1.10 or later.
- 7. Schedule a maintenance window and follow Dell's standard upgrade procedure for Data Domain systems.
- 8. After upgrade, verify the new version is installed using 'version' 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-43890 — 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-43890 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