CVE-2025-29987
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) versions prior to 8.3.0.15 contain an Insufficient Granularity of Access Control vulnerability. An authenticated user from a trusted remote client could exploit this vulnerability to execute arbitrary commands with root privileges.
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 systems running DD OS versions before 8.3.0.15 have an Insufficient Granularity of Access Control flaw. Authenticated users from trusted remote clients can bypass intended authorization boundaries and execute arbitrary operating system commands with root-level privileges.
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.10.1.60>= 7.10.1.0, < 7.10.1.60>= 7.13.1.0, < 7.13.1.25>= 8.3.0.0, < 8.3.0.15>= 5.12, < 5.19.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 DD OS versionLog into the Data Domain CLI via SSH or console and run the command `ddr version` or `system show version` to obtain the exact OS version numberAffected if The version displayed falls within these ranges: 7.10.1.0 to 7.10.1.59, 7.13.1.0 to 7.13.1.24, 8.3.0.0 to 8.3.0.14, or is earlier than 7.10.1.60 on systems older than 7.10.1.0
-
Confirm remote CLI access is enabledCheck if SSH or other remote management access is permitted to the Data Domain system. This can be verified via the `services show` command or by reviewing the access list configurationAffected if Remote SSH or CLI access is enabled and reachable from network segments containing trusted clients
-
Review user authentication configurationExamine the Data Domain user authentication settings using `user show` or `authentication show` to identify the number and type of configured users with CLI accessAffected if Non-administrator users exist who have CLI login capability from remote locations
-
Inspect system audit logs for privileged command executionReview DD OS audit logs using `audit log show` or by examining /ddr/logs/audit for commands executed with elevated privileges, especially from remote sessionsAffected if Audit logs show privileged commands (such as those requiring root) executed by users logged in from remote IP addresses
A system is affected if it runs a DD OS version matching one of the affected ranges listed and has remote CLI authentication enabled for users who could potentially bypass authorization boundaries to execute root-level commands.
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 · scoped5.19.0.07.10.1.607.13.1.25
Upgrade Dell PowerProtect Data Domain to DD OS version 8.3.0.15 or later to obtain the vendor patch that enforces proper access control boundaries between authenticated users and root-level command execution.
Upgrade to DD OS 7.10.1.60, 7.13.1.25, or 8.3.0.15 (or Powerprotect DM5500 Firmware 5.19.0.0) depending on product line
- 1. Identify the current version of Dell PowerProtect Data Domain or Data Domain Operating System by running 'ddboost show system' or checking the system management interface
- 2. Determine the appropriate upgrade path based on current version (7.10.x -> 7.10.1.60, 7.13.x -> 7.13.1.25, 8.3.x -> 8.3.0.15, or DM5500 -> 5.19.0.0)
- 3. Schedule a maintenance window and create a full system backup or snapshot before proceeding
- 4. Download the appropriate Dell PowerProtect Data Domain DD OS upgrade package from Dell Support (support.dell.com)
- 5. Upload the upgrade file to the Data Domain system using the admin interface or SCP
- 6. Execute the upgrade using the 'system upgrade' command or through the management GUI, following Dell's official upgrade documentation
- 7. Verify the upgrade completed successfully by checking the system version matches the target fixed release
- 8. Confirm the vulnerability is remediated by verifying the access control fixes are applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29987 — 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-29987 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