LiveActive security incident?Get immediate response
CVE Record

CVE-2011-2057: The cat6000-dot1x component in Cisco IOS 12.2 before 12.2(33)SXI7 does not properly handle (1) a loop betwe...

The cat6000-dot1x component in Cisco IOS 12.2 before 12.2(33)SXI7 does not properly handle (1) a loop between a dot1x enabled port and an open-authentication dot1x enabled port and (2) a loop between a dot1x enabled port and a non-dot1x port, which allows remote attackers to cause a denial of service (traffic storm) via unspecified vectors that trigger many Spanning Tree Protocol (STP) Bridge Protocol Data Unit (BPDU) frames, aka Bug ID CSCtq36327.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw can let an attacker cause a network traffic storm in affected Cisco IOS 12.2 cat6000-dot1x handling. The business risk is availability: impacted switching environments could experience disruption rather than data theft. The provided sources do not include CVSS scoring, confirmed exploitation, or detailed workaround guidance. Exposure appears limited to environments running Cisco IOS 12.2 before 12.2(33)SXI7 with affected cat6000-dot1x configurations. Highest concern is switching infrastructure where dot1x and mixed authentication port states are present. The source bundle does not provide complete CPE or product inventory data. Treat as a network availability risk, not a confirmed breach indicator. Prioritize if legacy Cisco IOS switching remains in production, especially in critical sites. If affected infrastructure is retired or upgraded, urgency is lower but should still be documented. Mitigation focus: Upgrade affected Cisco IOS 12.2 deployments to 12.2(33)SXI7 or later guidance-supported software.; Review Cisco release notes and advisories for CSCtq36327-specific guidance.; Identify and correct risky loops involving dot1x, open-authentication dot1x, and non-dot1x ports..

Prepared

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.

cve · low confidence lookup

CVE-2011-2057 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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