CVE-2025-36565
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 Argument Delimiters in a Command ('Argument Injection') vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to arbitrary command execution. Exploitation may allow privilege escalation to root.
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 confidenceThis is an argument injection vulnerability in Dell PowerProtect Data Domain's DD OS command interface. A high-privileged local attacker can inject arbitrary command arguments, potentially achieving root privilege escalation. The vulnerability affects multiple feature release and LTS versions spanning 7.7.1.0 through 8.1.0.10.
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.13.1.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 the installed Dell Data Domain OS versionAccess the Data Domain management interface or run 'version' command via SSH/console to retrieve the DD OS version numberAffected if The displayed version falls within these ranges: 7.7.1.0 to 7.10.1.59, 7.13.1.0 to 7.13.1.29, or 8.0.0.0 to 8.3.0.9
-
Confirm the specific feature release or LTS branchCheck whether the system is running a Feature Release (7.7.x, 7.8.x, 7.9.x, 8.0.x, 8.1.x, 8.2.x) or an LTS release (7.10.x, 7.13.x) and note the exact subversionAffected if The branch and version number match the affected ranges in step 1
-
Determine if the DD OS command interface is accessibleVerify whether the command-line interface is enabled and accessible for high-privileged local users (typically via admin/root accounts)Affected if The command interface is enabled and the system has high-privileged local user accounts configured
The environment is affected if the installed DD OS version falls within any of the three vulnerable version ranges (7.7.1.0-7.10.1.59, 7.13.1.0-7.13.1.29, or 8.0.0.0-8.3.0.9) AND the DD OS command interface is accessible to high-privileged local users.
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 Dell-provided patches/updates to the Data Domain OS; restrict local access to trusted high-privileged users and monitor for suspicious command execution.
Upgrade to DD OS 7.10.1.60 or later (for 7.10.x branch), 7.13.1.30 or later (for 7.13.x branch), or 8.3.0.10 or later (for 8.x branch) - prefer 8.3.0.10 or later if feasible
- 1. Identify the current Data Domain Operating System (DD OS) version using the 'version' command or through the Data Domain System Manager web interface.
- 2. Based on the current version, determine the appropriate upgrade path:
- - If running 7.7.1.0 through 7.10.1.59: upgrade to DD OS version 7.10.1.60 or later
- - If running 7.13.1.0 through 7.13.1.29: upgrade to DD OS version 7.13.1.30 or later
- - If running 8.0.0.0 through 8.3.0.9: upgrade to DD OS version 8.3.0.10 or later
- 3. Download the appropriate DD OS upgrade package from Dell Support (www.dell.com/support) for the target version.
- 4. Review Dell PowerProtect Data Domain upgrade documentation for pre-upgrade requirements and procedures.
- 5. Execute the upgrade following Dell's standard DD OS upgrade procedure, typically via the 'software' command or through the System Manager.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36565 — 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-36565 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