CVE-2025-46645
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, LTS 2023 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 remote 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 Data Domain OS versions 7.7.1.0 through 8.4.0.0 and various LTS releases contain an OS Command Injection vulnerability. The flaw allows a high-privileged attacker with remote access to execute arbitrary OS commands due to improper neutralization of special elements in system 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.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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 Data Domain OS versionAccess the appliance CLI and run the command to display the system version (commonly 'version' or 'system show version'), or check the login banner which typically displays the DD OS version on connectionAffected if The displayed version falls within any of these ranges: 7.7.1.0 through 7.10.1.79, 7.13.1.0 through 7.13.1.49, 8.3.1.0 through 8.3.1.19, or equals exactly 8.4.0.0
-
Confirm remote administrative access is enabledReview the system access configuration settings through the DD OS CLI (often under 'access' or 'network' configuration modes) to determine if remote administrative protocols such as SSH or the management GUI are enabled for external networksAffected if Remote administrative access (SSH, HTTPS management interface) is enabled and accessible from untrusted networks
-
Audit command execution logs for suspicious activityReview DD OS system logs and command history (typically accessible via 'logs show' or 'support' commands in the CLI) for any unauthorized or unexpected commands executed around the time of potential compromiseAffected if Logs contain commands or operations not initiated by known administrators, or show evidence of command injection patterns (such as unusual characters or unexpected command chaining)
-
Review administrative session historyCheck the system's session logs or audit trails (often available through 'session show' or 'audit log' commands) for any sessions from high-privileged accounts that appear unusual or originated from unexpected sourcesAffected if Administrative sessions show connections from unknown IP addresses or exhibit behavior inconsistent with normal administrative operations
A user is affected if their Data Domain OS version matches any of the affected version ranges AND the system allows remote administrative access, making it vulnerable to command injection by a high-privileged attacker.
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 the vendor-supplied patch or upgrade to a fixed DD OS version. Prior to patching, restrict remote administrative access and monitor for suspicious command activity.
DD OS 7.10.1.80+ (for 7.7.x/7.10.x), 7.13.1.50+ (for 7.13.x), 8.3.1.20+ (for 8.3.x), or next release after 8.4.0.0
- 1. Identify the current Data Domain Operating System (DD OS) version by running 'ddr version' or accessing the Management UI.
- 2. Determine which release track your system is on: Feature Release, LTS2023, LTS2024, or LTS2025.
- 3. For Feature Release 7.7.x: Upgrade to DD OS version 7.10.1.80 or later.
- 4. For LTS 2023 (7.10.x): Upgrade to DD OS version 7.10.1.80 or later.
- 5. For LTS 2024 (7.13.x): Upgrade to DD OS version 7.13.1.50 or later.
- 6. For LTS2025 (8.3.x): Upgrade to DD OS version 8.3.1.20 or later.
- 7. For Feature Release 8.4.0.0: Upgrade to the next available feature release version after 8.4.0.0 (contact Dell support for latest available version).
- 8. Download the appropriate DD OS upgrade package from Dell Support (support.dell.com).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46645 — 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-46645 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