CVE-2025-30097
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 · moderate confidenceDell PowerProtect Data Domain systems running DD OS contain an OS command injection vulnerability in the DDSH CLI component. An authenticated high-privilege attacker with local access can inject arbitrary OS commands that execute with root privileges, allowing complete system compromise.
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.
-
Identify DD OS versionLog into the Data Domain system and run the command to display the operating system version, such as 'ddr version' or 'system show version' from the admin console.Affected if The displayed version falls within any of these ranges: 7.7.1.0 through 7.10.1.59, 7.11.0.0 through 7.13.1.29, or 8.0.0.0 through 8.3.0.9
-
Confirm DDSH CLI is accessibleVerify that the DDSH CLI component is available on the system. On Data Domain systems, DDSH is typically accessed via 'ddsh' command or through the admin shell. Confirm you can enter the DDSH interface.Affected if DDSH CLI is present and accessible on the system
-
Check authenticated user privilegesDetermine the privilege level of your current authenticated session in DDSH. Identify if the user has high-privilege administrative access (such as admin or equivalent root-level privileges).Affected if The authenticated user has high-privilege administrative access to DDSH
-
Verify local access contextConfirm the access method being used to reach the DDSH CLI. This vulnerability requires local access rather than remote network access.Affected if The attacker has local console or direct access to the system, not just remote access
A system is affected if it runs a DD OS version in the vulnerable ranges AND has an authenticated high-privilege user with local access to the DDSH CLI, allowing potential root-level command injection.
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 or upgrade to a fixed version beyond 8.1.0.10 (Feature Release), 7.13.1.25 (LTS2024), or 7.10.1.50 (LTS2023). Limit local access to trusted administrators and monitor DDSH CLI usage for suspicious activity.
DD OS 7.10.1.60 (LTS 2023) / 7.13.1.30 (LTS2024) / 8.3.0.10 depending on your release track
- 1. Identify the current Data Domain Operating System (DD OS) version by running 'system show version' on the DDSH CLI.
- 2. Determine which version range your current DD OS falls into (7.7.1.0-7.10.1.x, 7.11.0.0-7.13.1.x, or 8.0.0.0-8.3.0.x).
- 3. For DD OS 7.7.1.x-7.10.1.x: Upgrade to LTS 2023 release version 7.10.1.60 or later.
- 4. For DD OS 7.11.0.x-7.13.1.x: Upgrade to LTS2024 release version 7.13.1.30 or later.
- 5. For DD OS 8.0.0.x-8.3.0.x: Upgrade to version 8.3.0.10 or later.
- 6. Download the appropriate DD OS upgrade package from Dell Support (support.dell.com) - you will need a valid Dell support account.
- 7. Review Dell Data Domain upgrade documentation and release notes before proceeding.
- 8. Execute the upgrade following Dell's standard DD OS upgrade procedure, typically using 'software upgrade' command or the Data Domain Management Center (DDMC).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30097 — 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-30097 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