CVE-2025-46644
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.4.0.0, LTS2025 release version 8.3.1.10, LTS2024 release versions 7.13.1.0 through 7.13.1.40, LTS2023 release versions 7.10.1.0 through 7.10.1.70, 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 Command execution.
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 appliances running DD OS versions 7.7.1.0 through 8.4.0.0 (and specific LTS releases) contain an OS command injection vulnerability (CWE-78). A high-privileged local attacker can inject arbitrary OS commands due to improper neutralization of special elements in the operating system command, potentially achieving full command execution on the affected Data Domain system.
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.80>= 7.13.1.0, < 7.13.1.50>= 8.3.1.0, < 8.3.1.20= 8.4.0.0CVSS 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 system as a Dell Data Domain applianceCheck system identification (e.g., hardware model, system inventory, or boot messages) to confirm it is a Dell PowerProtect Data Domain appliance rather than a generic server.Affected if The system is not a Dell Data Domain appliance, the vulnerability does not apply.
-
Determine the installed DD OS versionRetrieve the Data Domain Operating System version from the system (e.g., via system info command, CLI show command, or management interface).Affected if Unable to determine the DD OS version prevents assessment of exposure.
-
Compare the installed version against affected rangesCheck if the installed version falls within any of these ranges: 7.7.1.0 to 7.10.1.80 (exclusive of 7.10.1.80), 7.13.1.0 to 7.13.1.50 (exclusive of 7.13.1.50), 8.3.1.0 to 8.3.1.20 (exclusive of 8.3.1.20), or exactly 8.4.0.0.Affected if The installed DD OS version matches any of these ranges or the specific version 8.4.0.0, the system falls within the affected population.
-
Verify presence of high-privileged local accountsReview local user accounts with elevated privileges on the Data Domain system (e.g., admin, root, or equivalent privileged DD OS accounts).Affected if High-privileged local accounts exist on an affected system, the command injection vulnerability could be exploited by an attacker with access to those accounts.
If the system is a Dell Data Domain appliance running DD OS version 7.7.1.0 through 8.4.0.0 (excluding patched subversions), it is affected by this OS command injection vulnerability.
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.807.13.1.508.3.1.20
Apply vendor-supplied patches or firmware updates for DD OS once released. Until then, strictly limit local access to trusted high-privileged accounts only and implement enhanced audit logging of administrative command execution.
7.10.1.80 (or later 7.10.1.x) for LTS2023; 7.13.1.50 (or later 7.13.x) for LTS2024; 8.3.1.20 (or later 8.3.x) for LTS2025
- 1. Identify the current Data Domain Operating System (DD OS) version using the DD OS CLI command: `version`
- 2. Determine which version branch your current installation belongs to (7.7.x-7.9.x, 7.10.x, 7.13.x, 8.3.x, or 8.4.0)
- 3. For branch 7.7.1.0-7.9.x: Plan upgrade to 7.10.1.80 or later LTS2023 release (7.10.1.x)
- 4. For branch 7.10.1.0-7.10.1.70: Upgrade to 7.10.1.80 or later
- 5. For branch 7.13.1.0-7.13.1.40: Upgrade to 7.13.1.50 or later LTS2024 release
- 6. For branch 8.3.1.0-8.3.1.10: Upgrade to 8.3.1.20 or later LTS2025 release
- 7. For branch 8.4.0.0: Upgrade to the next available patched release (8.3.1.20 or later, or 8.5.x if available)
- 8. Before upgrading, review Dell PowerProtect Data Domain release notes for any prerequisites and compatibility requirements
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46644 — 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-46644 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