CVE-2025-46606
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 8.4 through 8.5 contain an improper restriction of excessive authentication attempts vulnerability. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to unauthorized access.
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 versions 8.4 through 8.5 contain an improper restriction of excessive authentication attempts vulnerability. The system fails to properly limit, throttle, or lock out authentication attempts after failed login tries, allowing a high-privileged remote attacker to conduct brute-force attacks against valid accounts until credentials are compromised.
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>= 8.4.0.0, < 8.6.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 DD OS versionAccess the Data Domain management interface or CLI and retrieve the operating system version. This is typically available through the web-based management console or by running a version command from the administrative shell.Affected if The installed version is 8.4.0.0 through 8.5.x (any 8.4.x or 8.5.x release), which falls within the vulnerable range >= 8.4.0.0 and < 8.6.0.0
-
Verify remote authentication is enabledReview the Data Domain system configuration to determine if remote authentication methods such as LDAP, Active Directory, or remote SSH access are enabled and accessible from network locations.Affected if Remote authentication services are exposed to network access, as this allows the brute-force attack vector to be exploited
-
Confirm user accounts existReview the list of configured local or domain user accounts that can authenticate to the Data Domain system.Affected if Valid user accounts exist in the system, as these become potential targets for brute-force credential attacks
-
Check authentication lockout configurationExamine the system's authentication security settings to determine if account lockout thresholds, login attempt limits, or account temporary disablement after failed attempts are configured.Affected if No account lockout or throttling mechanism is enforced, which means the system is vulnerable to unlimited authentication attempts
A user is affected if their Dell Data Domain system runs DD OS version 8.4.x or 8.5.x with remote authentication accessible and no account lockout controls in place.
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 · scoped8.6.0.0
Apply Dell-provided patches for DD OS Feature Release 8.4 and 8.5 as specified in vendor security advisories. If no patch is immediately available, implement compensating controls such as network access restrictions, multi-factor authentication, or account lockout policies at upstream authentication sources.
Data Domain Operating System 8.6.0.0 or later
- Verify current Data Domain Operating System version using 'ddboost show unit' or system CLI
- Schedule a maintenance window for the upgrade process
- Backup the current DD OS configuration using 'config export' or the management GUI
- Upgrade to DD OS version 8.6.0.0 or later following the Dell upgrade guide for PowerProtect Data Domain
- After upgrade, verify the system is operational and confirm the new version using 'version' command
- Verify the authentication configuration settings post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46606 — 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-46606 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