CVE-2025-36567
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-8.1.0.10, LTS2024 versions 7.13.1.0-7.13.1.25, and LTS2023 versions 7.10.1.0-7.10.1.50. A high-privileged authenticated attacker with local access can inject arbitrary OS commands, potentially achieving root privilege escalation.
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 installed DD OS versionAccess the Data Domain management console or run 'ddos -version' via CLI. On the appliance, use the 'system show version' command or check the GUI under System > Overview > Software Version.Affected 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.
-
Confirm local or console access is enabledReview physical access controls, serial console configuration, and IPMI/DRAC remote management settings. Check if console or local SSH access is permitted from non-secured network segments.Affected if Unrestricted local or console access exists for non-administrative personnel or from shared/network-accessible console ports.
-
Audit high-privileged local accountsUse 'user -list' or view accounts via the DD OS administration interface. Identify accounts with elevated privileges beyond standard operational needs.Affected if Multiple high-privileged accounts exist, especially accounts with root-level access beyond the minimum required for system administration.
-
Review command execution logs for anomaliesExamine DD OS system logs, audit logs, and shell history for unexpected or unauthorized command execution patterns. Check logs under /ddr/logs/ or via the GUI logging facilities.Affected if Logs show commands executed by high-privileged users that are unusual, unexpected, or indicate privilege escalation attempts.
Your environment is affected if the DD OS version matches the vulnerable ranges AND an attacker could obtain high-privileged authenticated local access to the appliance.
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 the vendor-supplied patch or firmware update to the latest supported DD OS version. Restrict local access to only necessary high-privileged personnel and monitor for suspicious command execution.
DD OS 7.10.1.60 (LTS 2023 branch), 7.13.1.30 (LTS2024 branch), or 8.3.0.10 (Feature Release branch) depending on current release track
- 1. Identify the current Data Domain Operating System (DD OS) version installed on the affected system using the 'ddos' CLI: 'system show version'
- 2. Determine which release branch the current version belongs to (LTS 2023, LTS2024, or Feature Release) based on the version number
- 3. For systems on Feature Release (7.7.1.x - 7.10.1.x): Schedule maintenance window and upgrade to version 7.10.1.60 or later
- 4. For systems on LTS2024 (7.13.1.x): Schedule maintenance window and upgrade to version 7.13.1.30 or later
- 5. For systems on Feature Release 8.x (8.0.0.x - 8.3.x): Schedule maintenance window and upgrade to version 8.3.0.10 or later
- 6. After upgrade, verify the new version is installed: 'ddos -r' and confirm version number
- 7. Validate that the fix is applied by checking release notes for the fixed version confirm OS Command Injection vulnerability is addressed
- 8. Test that normal DD OS operations function correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36567 — 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-36567 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