CVE-2025-36594
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.3.0.15, LTS2024 release Versions 7.13.1.0 through 7.13.1.25, LTS 2023 release versions 7.10.1.0 through 7.10.1.60, contain an Authentication Bypass by Spoofing vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Protection mechanism bypass. Remote unauthenticated user can create account that potentially expose customer info, affect system integrity and availability.
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 · moderate confidenceDell PowerProtect Data Domain systems running DD OS contain an authentication bypass vulnerability where unauthenticated remote attackers can create administrative accounts by spoofing authentication. This allows complete system compromise, exposing customer backup data, modifying system integrity, and disrupting availability.
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.70>= 7.13.1.0, < 7.13.1.30>= 8.0.0.0, < 8.3.1.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Data Domain systemLog into the system and run the command to display the DD OS version, typically via 'ddos' or 'system' commands available on the applianceAffected if The system is not a Dell PowerProtect Data Domain or Dell Data Domain appliance
-
Determine the installed DD OS versionExecute the command to display the current DD OS version installed on the systemAffected if The version falls within >= 7.7.1.0 and < 7.10.1.70, OR >= 7.13.1.0 and < 7.13.1.30, OR >= 8.0.0.0 and < 8.3.1.0
-
Review administrative user accountsUse the administrative interface or CLI to list all configured administrative accounts and look for any unauthorized or unknown accounts that were not created by your organizationAffected if Unexpected administrative accounts exist that were not created by legitimate administrators
-
Check management interface network exposureReview network configuration to determine if the management interface (typically ports 22, 443, or 3000) is accessible from untrusted networks or the internetAffected if Management interfaces are exposed directly to the internet or untrusted networks without VPN or firewall controls
A user is affected if they are running a Dell Data Domain system with DD OS versions within the specified vulnerable ranges and the management interface is network-accessible to potential attackers.
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.707.13.1.308.3.1.0
Apply Dell-provided patches or upgrade to non-vulnerable versions as specified in Dell Security Advisory DSA-2025-183. Restrict network access to management interfaces until patches are applied.
Upgrade to DD OS 7.10.1.70 (LTS 2023), 7.13.1.30 (LTS 2024), or 8.3.1.0 (Feature Release) depending on your current branch
- 1. Identify the current Data Domain Operating System (DD OS) version installed on the Dell PowerProtect Data Domain system
- 2. Determine which version branch the current installation belongs to (LTS 2023: 7.10.x, LTS 2024: 7.13.x, or Feature Release: 7.7.x-8.x)
- 3. For systems running LTS 2023 (7.10.1.0-7.10.1.60), upgrade to version 7.10.1.70 or later
- 4. For systems running LTS 2024 (7.13.1.0-7.13.1.25), upgrade to version 7.13.1.30 or later
- 5. For systems running Feature Release (7.7.1.0-8.3.0.15), upgrade to version 8.3.1.0 or later
- 6. Verify the upgrade was successful by confirming the new OS version in the Data Domain management interface
- 7. Validate that the authentication mechanism is functioning correctly after upgrade
- 8. Review system logs for any suspicious account creation attempts that may have occurred prior to patching
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36594 — 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-36594 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