LiveActive security incident?Get immediate response
CVE Record

CVE-2020-26062: 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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-26062 lets an unauthenticated remote attacker confirm whether administrator usernames exist in Cisco Integrated Management Controller. It does not grant access by itself, but it can improve follow-on password guessing, phishing, or credential-stuffing attempts against management interfaces.

Executive priority

Treat as a moderate-priority infrastructure management exposure. It is not a direct system takeover, but it weakens account security on sensitive management planes and should be remediated during normal patch cycles, faster if CIMC is broadly reachable.

Technical view

The issue is a username enumeration flaw caused by different authentication responses during login attempts. Cisco lists it as CWE-203 with CVSS 3.1 score 5.3, network exploitable, low complexity, no privileges, no user interaction, and low confidentiality impact. The source states there are no workarounds.

Likely exposure

Exposure is most relevant where Cisco Unified Computing System (Managed) versions listed in the source run Cisco Integrated Management Controller and the management interface is reachable by untrusted or broad internal networks.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The realistic risk is reconnaissance: attackers can validate administrative usernames, then use that knowledge in later credential attacks against infrastructure management systems.

Researcher notes

Evidence supports unauthenticated remote username enumeration through authentication response differences. The affected version list is specific, but the supplied bundle does not include fixed release details. Avoid claiming exploitation or exploit availability from these sources.

Mitigation direction

  • Check Cisco advisory cisco-sa-cimc-enum-CyheP3B7 for fixed software guidance.
  • Apply Cisco-recommended updates for affected UCS/CIMC deployments.
  • Do not rely on a workaround; the source states none exists.
  • Restrict CIMC management access to trusted administration networks.
  • Monitor authentication events for unusual username probing patterns.

Validation and detection

  • Inventory Cisco Unified Computing System (Managed) deployments using CIMC.
  • Compare installed versions with the affected versions in the source bundle.
  • Confirm CIMC interfaces are not exposed to the public internet.
  • Review authentication logs for repeated failed username discovery patterns.
  • Track Cisco advisory status before closing remediation.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-203: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-26062 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/RL:X/RC:X/E:X

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/RL:X/RC:X/E:X3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2020-26062Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/RL:X/RC:X/E:X

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
CiscoCisco Unified Computing System (Managed)4.0(1a), 3.2(3n), 4.1(1a), 4.1(1b), 4.0(4h), 4.1(1c), 3.2(3k), 3.2(2c), 4.0(4e), 4.0(4g), 3.2(3i), 4.0(2e), 3.2(3g), 4.0(4a), 4.0(2d), 3.2(2d), 4.0(1b), 4.0(4f), 3.2(3h), 3.2(2f), 4.0(4c), 3.2(3a), 4.0(1c), 3.2(3d), 3.2(2b), 4.0(4b), 3.2(2e), 4.0(2b), 4.0(4d), 3.2(1d), 3.2(3e), 3.2(3l), 3.2(3b), 4.0(2a), 3.2(3j), 4.0(1d), 3.2(3o), 4.0(4i), 4.1(1d), 4.1(2a), 4.1(1e), 3.2(3p)unknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-203 · source CWE mapping

Observable Discrepancy

Observable Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.