CVE-2025-36566
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. 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 confidenceDell PowerProtect Data Domain appliances running DD OS contain an OS Command Injection vulnerability in Feature Release versions 7.7.1.0 through 8.1.0.10, LTS2024 versions 7.13.1.0 through 7.13.1.25, and LTS2023 versions 7.10.1.0 through 7.10.1.50. An authenticated high-privileged local attacker can inject arbitrary OS commands, potentially escalating privileges to root.
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.
-
Check DD OS versionLog into the Data Domain CLI and run 'ddr version' or 'system show version' to obtain the installed DD OS versionAffected if The installed version falls within 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 (or you are on a Feature Release between 7.7.1.0 and 8.1.0.10, LTS2024 between 7.13.1.0 and 7.13.1.25, or LTS2023 between 7.10.1.0 and 7.10.1.50)
-
Verify local admin access existsCheck for locally-defined high-privileged administrator accounts using 'user show' or 'admin show' command in DD OS CLI. These are distinct from directory-based (LDAP/AD) accounts.Affected if Local high-privileged accounts are configured and accessible, providing authenticated access to the system
-
Confirm SSH or console access is enabledVerify that SSH or console login is permitted for admin users by checking 'access' or 'ssh' configuration settings via 'access show' or 'ssh status'Affected if SSH or console access is enabled, allowing authenticated users to reach the CLI where command injection occurs
-
Check for unusual admin activityReview DD OS audit logs or system logs for commands executed by high-privileged users, looking for suspicious or unexpected command patternsAffected if Evidence exists of arbitrary command execution by non-root admin users, indicating active exploitation
You are affected if your DD OS version is within the vulnerable ranges and local high-privileged authentication is available (since exploitation requires an authenticated local 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.607.13.1.308.3.0.10
Apply vendor-supplied patches for DD OS once released; in the interim, strictly limit local access to trusted, vetted administrators and monitor for unauthorized access attempts.
DD OS 8.3.0.10 or later (latest stable 8.x release)
- 1. Identify the current Data Domain Operating System (DD OS) version running on the affected Dell PowerProtect Data Domain system via the system CLI or management interface.
- 2. Determine which version branch the current system is running (7.7.x-7.10.x, 7.13.x, or 8.0.x-8.3.x).
- 3. For systems on the 7.10.x branch (versions 7.7.1.0 through 7.10.1.50): upgrade to version 7.10.1.60 or later.
- 4. For systems on the 7.13.x branch (LTS2024, versions 7.13.1.0 through 7.13.1.25): upgrade to version 7.13.1.30 or later.
- 5. For systems on the 8.x branch (versions 8.0.0.0 through 8.1.0.10): upgrade to version 8.3.0.10 or later.
- 6. Plan the upgrade during a maintenance window as the system may require downtime.
- 7. Back up the current system configuration before performing the upgrade.
- 8. Apply the upgrade following Dell's standard DD OS upgrade procedures using the Data Domain Management Center or CLI.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36566 — 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-36566 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