Unauthenticated LDAP username enumeration via authentication requests
Published Apr 16, 2025 · Updated Apr 16, 2025
Information disclosure in Cisco Nexus Dashboard before 3.2(2f) allows remote attackers to enumerate LDAP accounts via login requests. The LDAP authentication path improperly handles supplied usernames and reveals whether each one maps to a valid account; Cisco has not disclosed the precise response distinction. Exposure requires LDAP to be configured as a remote authentication provider, and the reported consequence is disclosure of valid usernames only.
Summary
What happened
Information disclosure in Cisco Nexus Dashboard before 3.2(2f) allows remote attackers to enumerate LDAP accounts via login requests. The LDAP authentication path improperly handles supplied usernames and reveals whether each one maps to a valid account; Cisco has not disclosed the precise response distinction. Exposure requires LDAP to be configured as a remote authentication provider, and the reported consequence is disclosure of valid usernames only.
The record
- CVE
- CVE-2025-20150
- Published
- Apr 16, 2025
- Updated
- Apr 16, 2025
- Vendor
- ClamAV
- Product
- Cisco Nexus Dashboard
- Classifications
- CWE-209, T1087.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2025CVE publishedPublication date reported by the CVE source.
- Apr 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0(1b)
- Affected versionversion=2.0(1d)
- Affected versionversion=2.0(2g)
- Affected versionversion=2.0(2h)
- Affected versionversion=2.1(1d)
- Affected versionversion=2.1(1e)
- Affected versionversion=2.1(2d)
- Affected versionversion=2.1(2f)
- Affected versionversion=2.2(1e)
- Affected versionversion=2.2(1h)
- Affected versionversion=2.2(2d)
- Affected versionversion=2.3(1c)
- Affected versionversion=2.3(2b)
- Affected versionversion=2.3(2c)
- Affected versionversion=2.3(2d)
- Affected versionversion=2.3(2e)
- Affected versionversion=3.0(1f)
- Affected versionversion=3.0(1i)
- Affected versionversion=3.1(1k)
- Affected versionversion=3.1(1l)
- Affected versionversion=3.2(1e)
- Affected versionversion=3.2(1i)
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo