dbcve.org
Nexus DashboardApplication · Cisco

CVE-2025-20150

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-16
Fix available
A fix is available. Upgrade to 3.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability in Cisco Nexus Dashboard could allow an unauthenticated, remote attacker to enumerate LDAP user accounts. This vulnerability is due to the improper handling of LDAP authentication requests. An attacker could exploit this vulnerability by sending authentication requests to an affected system. A successful exploit could allow an attacker to determine which usernames are valid LDAP user accounts.

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 confidence

This is an LDAP user enumeration vulnerability in Cisco Nexus Dashboard. The application improperly handles LDAP authentication requests, allowing an unauthenticated remote attacker to determine valid usernames by analyzing differences in authentication response messages or timing between existing and non-existing LDAP accounts.

MitigationApply Cisco's patch when available. Until then, implement compensating controls such as uniform error responses for failed authentication (to prevent username enumeration), rate limiting on authentication endpoints, and monitoring for enumeration patterns.

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
Nexus DashboardApplication
Affected:< 3.2\(2f\)

CVSS 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco Nexus Dashboard version
    Access the Nexus Dashboard admin interface or use the CLI command 'show version' to retrieve the installed software version. Compare against the affected range: versions prior to 3.2(2f).
    Affected if The installed version is Cisco Nexus Dashboard < 3.2(2f)
  2. Confirm LDAP authentication is enabled
    Navigate to the Nexus Dashboard administration settings and verify if LDAP/LDAP authentication integration is configured and active for user authentication.
    Affected if LDAP authentication is enabled on the Nexus Dashboard
  3. Inspect LDAP authentication response configuration
    Review the LDAP authentication configuration settings to determine whether error messages returned for failed login attempts are uniform regardless of whether the username exists in the LDAP directory.
    Affected if Failed authentication responses differ between valid and invalid usernames (non-uniform errors)
  4. Review authentication endpoint rate limiting
    Check if rate limiting or account lockout policies are configured on the LDAP authentication endpoints to limit rapid enumeration attempts.
    Affected if No rate limiting or account lockout is enforced on authentication endpoints

The environment is affected if running Cisco Nexus Dashboard version < 3.2(2f) with LDAP authentication enabled and without uniform error responses for failed authentication attempts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.2 or later
Fixed in 3.2
Interim mitigation

Apply Cisco's patch when available. Until then, implement compensating controls such as uniform error responses for failed authentication (to prevent username enumeration), rate limiting on authentication endpoints, and monitoring for enumeration patterns.

Recommended fix Moderate confidence

Nexus Dashboard 3.2(2f) or later

  1. 1. Back up the current Nexus Dashboard configuration and ensure you have a rollback plan.
  2. 2. Review Cisco Nexus Dashboard upgrade documentation for prerequisites and compatibility requirements.
  3. 3. Schedule a maintenance window as the upgrade may cause service interruption.
  4. 4. Download Cisco Nexus Dashboard version 3.2(2f) or later from the Cisco software download page.
  5. 5. Initiate the upgrade following Cisco's documented upgrade procedure for Nexus Dashboard.
  6. 6. After upgrade completes, verify the system is running the patched version.
  7. 7. Test LDAP authentication functionality to confirm the fix works and legitimate users can authenticate.
  8. 8. Monitor system logs to confirm no enumeration attempts are occurring.
Caveat Review Cisco release notes for version 3.2(2f) for any configuration or compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nexus Dashboard Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20150 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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