Username enumeration via authentication response discrepancies
Published Nov 18, 2024 · Updated Nov 18, 2024
Username enumeration in Cisco Integrated Management Controller 3.2, 4.0, and 4.1 UCS releases allows remote attackers to identify valid accounts. The authentication interface returns distinguishable responses for valid and invalid account names instead of a uniform failure. No authentication or user interaction is required; the result confirms administrative account names for use in further attacks.
Summary
What happened
Username enumeration in Cisco Integrated Management Controller 3.2, 4.0, and 4.1 UCS releases allows remote attackers to identify valid accounts. The authentication interface returns distinguishable responses for valid and invalid account names instead of a uniform failure. No authentication or user interaction is required; the result confirms administrative account names for use in further attacks.
The record
- CVE
- CVE-2020-26062
- Published
- Nov 18, 2024
- Updated
- Nov 18, 2024
- Vendor
- ClamAV
- Product
- Cisco Unified Computing System (Managed)
- Classifications
- CWE-203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 18, 2024CVE publishedPublication date reported by the CVE source.
- Nov 18, 2024Record 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=3.2(1d)
- Affected versionversion=3.2(2b)
- Affected versionversion=3.2(2c)
- Affected versionversion=3.2(2d)
- Affected versionversion=3.2(2e)
- Affected versionversion=3.2(2f)
- Affected versionversion=3.2(3a)
- Affected versionversion=3.2(3b)
- Affected versionversion=3.2(3d)
- Affected versionversion=3.2(3e)
- Affected versionversion=3.2(3g)
- Affected versionversion=3.2(3h)
- Affected versionversion=3.2(3i)
- Affected versionversion=3.2(3j)
- Affected versionversion=3.2(3k)
- Affected versionversion=3.2(3l)
- Affected versionversion=3.2(3n)
- Affected versionversion=3.2(3o)
- Affected versionversion=3.2(3p)
- Affected versionversion=4.0(1a)
- Affected versionversion=4.0(1b)
- Affected versionversion=4.0(1c)
- Affected versionversion=4.0(1d)
- Affected versionversion=4.0(2a)
- Affected versionversion=4.0(2b)
- Affected versionversion=4.0(2d)
- Affected versionversion=4.0(2e)
- Affected versionversion=4.0(4a)
- Affected versionversion=4.0(4b)
- Affected versionversion=4.0(4c)
- Affected versionversion=4.0(4d)
- Affected versionversion=4.0(4e)
- Affected versionversion=4.0(4f)
- Affected versionversion=4.0(4g)
- Affected versionversion=4.0(4h)
- Affected versionversion=4.0(4i)
- Affected versionversion=4.1(1a)
- Affected versionversion=4.1(1b)
- Affected versionversion=4.1(1c)
- Affected versionversion=4.1(1d)
- Affected versionversion=4.1(1e)
- Affected versionversion=4.1(2a)
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