Cisco IMC User Enumeration via Auth Response Timing
CVE-2020-26062 Published on November 18, 2024
Cisco Integrated Management Controller Username Enumeration Vulnerability
A vulnerability in Cisco Integrated Management Controller could allow an unauthenticated, remote attacker to enumerate valid usernames within the vulnerable application.
The vulnerability is due to differences in authentication responses sent back from the application as part of an authentication attempt. An attacker could exploit this vulnerability by sending authentication requests to the affected application. A successful exploit could allow the attacker to confirm the names of administrative user accounts for use in further attacks.There are no workarounds that address this vulnerability.
Vulnerability Analysis
CVE-2020-26062 is exploitable with network access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have a small impact on confidentiality, a small impact on integrity and availability.
Weakness Type
What is a Side Channel Attack Vulnerability?
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not. Discrepancies can take many forms, and variations may be detectable in timing, control flow, communications such as replies or requests, or general behavior. These discrepancies can reveal information about the product's operation or internal state to an unauthorized actor. In some cases, discrepancies can be used by attackers to form a side channel.
CVE-2020-26062 has been classified to as a Side Channel Attack vulnerability or weakness.
Products Associated with CVE-2020-26062
stack.watch emails you whenever new vulnerabilities are published in Cisco Unified Computing System or Cisco Integrated Management Controller. Just hit a watch button to start following.
Affected Versions
Cisco Unified Computing System (Managed):- Version 4.0(1a) is affected.
- Version 3.2(3n) is affected.
- Version 4.1(1a) is affected.
- Version 4.1(1b) is affected.
- Version 4.0(4h) is affected.
- Version 4.1(1c) is affected.
- Version 3.2(3k) is affected.
- Version 3.2(2c) is affected.
- Version 4.0(4e) is affected.
- Version 4.0(4g) is affected.
- Version 3.2(3i) is affected.
- Version 4.0(2e) is affected.
- Version 3.2(3g) is affected.
- Version 4.0(4a) is affected.
- Version 4.0(2d) is affected.
- Version 3.2(2d) is affected.
- Version 4.0(1b) is affected.
- Version 4.0(4f) is affected.
- Version 3.2(3h) is affected.
- Version 3.2(2f) is affected.
- Version 4.0(4c) is affected.
- Version 3.2(3a) is affected.
- Version 4.0(1c) is affected.
- Version 3.2(3d) is affected.
- Version 3.2(2b) is affected.
- Version 4.0(4b) is affected.
- Version 3.2(2e) is affected.
- Version 4.0(2b) is affected.
- Version 4.0(4d) is affected.
- Version 3.2(1d) is affected.
- Version 3.2(3e) is affected.
- Version 3.2(3l) is affected.
- Version 3.2(3b) is affected.
- Version 4.0(2a) is affected.
- Version 3.2(3j) is affected.
- Version 4.0(1d) is affected.
- Version 3.2(3o) is affected.
- Version 4.0(4i) is affected.
- Version 4.1(1d) is affected.
- Version 4.1(2a) is affected.
- Version 4.1(1e) is affected.
- Version 3.2(3p) is affected.
- Version 4.0\(1a\) is affected.
- Version 3.2\(3n\) is affected.
- Version 4.1\(1a\) is affected.
- Version 4.1\(1b\) is affected.
- Version 4.0\(4h\) is affected.
- Version 4.1\(1c\) is affected.
- Version 3.2\(3k\) is affected.
- Version 3.2\(2c\) is affected.
- Version 4.0\(4e\) is affected.
- Version 4.0\(4g\) is affected.
- Version 3.2\(3i\) is affected.
- Version 4.0\(2e\) is affected.
- Version 3.2\(3g\) is affected.
- Version 4.0\(4a\) is affected.
- Version 4.0\(2d\) is affected.
- Version 3.2\(2d\) is affected.
- Version 4.0\(1b\) is affected.
- Version 4.0\(4f\) is affected.
- Version 3.2\(3h\) is affected.
- Version 3.2\(2f\) is affected.
- Version 4.0\(4c\) is affected.
- Version 3.2\(3a\) is affected.
- Version 4.0\(1c\) is affected.
- Version 3.2\(3d\) is affected.
- Version 3.2\(2b\) is affected.
- Version 4.0\(4b\) is affected.
- Version 3.2\(2e\) is affected.
- Version 4.0\(2b\) is affected.
- Version 4.0\(4d\) is affected.
- Version 3.2\(1d\) is affected.
- Version 3.2\(3e\) is affected.
- Version 3.2\(3l\) is affected.
- Version 3.2\(3b\) is affected.
- Version 4.0\(2a\) is affected.
- Version 3.2\(3j\) is affected.
- Version 4.0\(1d\) is affected.
- Version 3.2\(3o\) is affected.
- Version 4.0\(4i\) is affected.
- Version 4.1\(1d\) is affected.
- Version 4.1\(2a\) is affected.
- Version 4.1\(1e\) is affected.
- Version 3.2\(3p\) is affected.
Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.