CVE-2025-43908
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 to execute arbitrary commands with root privileges.
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 contain an OS command injection vulnerability (CWE-78) across multiple Feature Release and LTS versions. The flaw allows a high-privileged attacker with local system access to execute arbitrary commands with root privileges due to improper neutralization of special elements in OS commands.
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 installed DD OS versionAccess the Data Domain system via console or SSH and run the command to display the system version (for example, via 'version' or 'system show version' command). Note the exact version number reported.Affected if The installed version falls within any of these 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, or 8.3.1.0 through 8.3.1.9.
-
Confirm local or console access is possibleDetermine whether the system permits local physical access via console or remote SSH access. Review the access control configuration to identify which users or groups have shell or console login privileges.Affected if Unrestricted or shared local/console access exists for multiple users, or SSH/shell access is enabled for accounts beyond a minimal trusted set.
-
Audit user accounts with elevated privilegesList all accounts that possess root-level or administrative privileges on the system. Review the sudoers configuration or equivalent access control files to identify which users can execute commands as root.Affected if Multiple high-privileged accounts exist, or accounts beyond the expected minimal set have root execution capabilities.
-
Review system logs for suspicious command executionExamine system command logs, shell history files, and audit logs for any unexpected or unauthorized command invocations, particularly those involving shell metacharacters or unusual argument patterns.Affected if Logs show command patterns containing shell injection indicators or commands executed by unexpected users at unusual times.
A system is affected if it runs a DD OS version within the specified ranges AND allows local or console access that could be exploited by a high-privileged local attacker to inject OS commands.
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-provided patches for the specific DD OS version; until then, strictly limit local physical and console access to trusted high-privileged users only and monitor for suspicious command execution.
7.10.1.70 (for LTS2023/feature releases), 7.13.1.40 (for LTS2024), 8.3.1.10 (for LTS2025)
- 1. Identify the currently installed Data Domain Operating System (DD OS) version using the 'ddos' command or system console
- 2. Determine which LTS/feature release branch your current version belongs to (LTS2023, LTS2024, LTS2025, or feature release 7.x/8.x)
- 3. Based on your current version branch, upgrade to the minimum fixed version: LTS2023 (7.10.x) upgrade to 7.10.1.70 or later; LTS2024 (7.13.x) upgrade to 7.13.1.40 or later; LTS2025 (8.3.1.x) upgrade to 8.3.1.10 or later; Feature release (7.7.x - 8.0.x) upgrade to 7.10.1.70 or later
- 4. Download the appropriate DD OS upgrade package from Dell Support (www.dell.com/support)
- 5. Follow Dell's standard DD OS upgrade procedure: upload the upgrade package to the Data Domain, validate the package, and execute the upgrade
- 6. After upgrade, verify the new version is running and confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing8.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,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43908 — 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-43908 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