CVE-2025-30099
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 low 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 confidenceOS Command Injection vulnerability in the DDSH CLI of Dell PowerProtect Data Domain. A low-privileged local attacker can 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.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 system as Dell Data DomainRun system identification commands (such as 'system show model' or 'hardware show') from the CLI to confirm the appliance is a Dell PowerProtect Data Domain deviceAffected if The system is not a Dell Data Domain appliance - this CVE only affects DD OS systems
-
Determine the installed DD OS versionExecute the command to display the Data Domain OS version (typically 'version' or 'system show version' from the CLI)Affected if Unable to retrieve the DD OS version - cannot determine if affected
-
Compare the installed version against affected rangesCheck if the installed version falls within: 7.7.1.0 <= version < 7.10.1.60, OR 7.11.0.0 <= version < 7.13.1.30, OR 8.0.0.0 <= version < 8.3.0.10Affected if The installed version matches any of the affected ranges listed above - the system is potentially vulnerable
-
Verify if low-privileged local users can access DDSH CLICheck user access controls and confirm whether non-privileged local accounts can execute DDSH CLI commands (review user role assignments and CLI access permissions)Affected if Low-privileged local users have access to the DDSH CLI interface - they can exploit the command injection flaw to gain root privileges
The system is affected if it is a Dell Data Domain appliance running a DD OS version within any of the three affected ranges AND low-privileged local users have 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-provided patches for DD OS versions 8.1.0.11+, 7.13.1.26+, and 7.10.1.51+ (or upgrade to newer LTS releases). Restrict local access to trusted users until patching is complete.
DD OS 7.10.1.60 (LTS2023), 7.13.1.30 (LTS2024), or 8.3.0.10 (Feature Release) depending on your release track
- 1. Identify the current Data Domain Operating System (DD OS) version using the 'version' command or through the DD System Management GUI
- 2. Determine the appropriate upgrade path based on current version (LTS2023, LTS2024, or Feature Release)
- 3. Download the appropriate DD OS update from Dell Support (support.dell.com) - ensure the target version meets or exceeds the fixed release for your track
- 4. Schedule a maintenance window as upgrades require system downtime
- 5. Back up the DD OS configuration using the 'ddr export' or 'config backup' command
- 6. Upload the DD OS upgrade file to the Data Domain using the 'software upload' command or via the GUI
- 7. Initiate the upgrade using the 'software install' command or via the GUI
- 8. Verify the upgrade completed successfully and the system is running the patched version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30099 — 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-30099 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