CVE-2025-30096
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.1.0.10, LTS2024 release Versions 7.13.1.0 through 7.13.1.25, LTS 2023 release versions 7.10.1.0 through 7.10.1.50, contain an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in the DDSH CLI. 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 devices running DD OS contain an OS command injection vulnerability in the DDSH CLI interface. The vulnerability allows a high-privileged local attacker to inject and execute arbitrary OS commands with root privileges due to improper neutralization of special elements in user input processed by the command-line interface.
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.60>= 7.11.0.0, < 7.13.1.30>= 8.0.0.0, < 8.3.0.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.
-
Confirm Dell Data Domain hardwareRun the command to display system hardware information (e.g., `system show hardware` or check the system boot logs for the model identifier)Affected if The system is not a Dell Data Domain device - this CVE only affects Dell PowerProtect Data Domain appliances
-
Determine DD OS versionExecute the command to display the DD OS version (e.g., `ddr version` or `software show`)Affected if Unable to retrieve the DD OS version - the system may not be a Data Domain or may use a different CLI command structure
-
Compare version against affected rangesTake the installed DD OS version from step 2 and compare it against the following ranges: 7.7.1.0 through 7.10.1.60, 7.11.0.0 through 7.13.1.30, or 8.0.0.0 through 8.3.0.10Affected if The installed version falls within any of the three affected ranges (inclusive of the lower bound, exclusive of the upper bound)
-
Verify high-privileged local access to DDSH CLIAttempt to access the DDSH CLI interface with elevated privileges (e.g., `ssh admin@dd-host` and then access the DDSH shell, or check if the current user has admin-level privileges in the CLI)Affected if High-privileged local or administrative CLI access is available - the vulnerability requires a high-privileged local attacker to inject commands through DDSH
The environment is affected if the system is a Dell Data Domain appliance running a DD OS version within any of the three affected ranges AND the attacker has high-privileged local access to the DDSH CLI interface.
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.607.13.1.308.3.0.10
Apply vendor-supplied patches to upgrade DD OS to a fixed version beyond 8.1.0.10, 7.13.1.25, or 7.10.1.50 as appropriate for the release track in use. Restrict local access to trusted, privileged users only until patching is complete.
DD OS 8.3.0.10 or later (or 7.13.1.30 for LTS2024, 7.10.1.60 for LTS2023)
- 1. Identify the current Data Domain Operating System (DD OS) version by running 'ddos version' or checking the system management interface.
- 2. Determine which version branch your current DD OS is on (Feature Release, LTS2023, LTS2024, or newer Feature Release).
- 3. For Feature Release versions: Upgrade to DD OS version 8.3.0.10 or later.
- 4. For LTS2024 release versions: Upgrade to DD OS version 7.13.1.30 or later.
- 5. For LTS2023 release versions: Upgrade to DD OS version 7.10.1.60 or later.
- 6. Download the appropriate DD OS upgrade package from Dell Support (support.dell.com) and follow the standard upgrade procedure.
- 7. After upgrade, verify the new version is installed by running 'ddos version' and confirm the vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30096 — 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-30096 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