CVE-2021-34767
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability in IPv6 traffic processing of Cisco IOS XE Wireless Controller Software for Cisco Catalyst 9000 Family Wireless Controllers could allow an unauthenticated, adjacent attacker to cause a Layer 2 (L2) loop in a configured VLAN, resulting in a denial of service (DoS) condition for that VLAN. The vulnerability is due to a logic error when processing specific link-local IPv6 traffic. An attacker could exploit this vulnerability by sending a crafted IPv6 packet that would flow inbound through the wired interface of an affected device. A successful exploit could allow the attacker to cause traffic drops in the affected VLAN, thus triggering the DoS condition.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA logic error in IPv6 link-local traffic processing in Cisco IOS XE Wireless Controller Software for Catalyst 9000 Family Wireless Controllers allows an adjacent, unauthenticated attacker to cause an L2 loop in a VLAN by sending a crafted IPv6 packet through the wired interface, resulting in traffic drops and DoS for the affected VLAN.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versions= 3.15.1xbs= 3.15.2xbs= 16.7.1= 16.7.1a= 16.7.1b= 16.7.2= 16.7.3= 16.7.4= 16.8.1= 16.8.1a= 16.8.1bCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device model and softwareRun 'show version' or 'show controller' to confirm the device is a Cisco Catalyst 9000 Family Wireless Controller running Cisco IOS XE softwareAffected if Device is a Cisco Catalyst 9000 Family Wireless Controller running IOS XE
-
Check the IOS XE versionRun 'show version' and examine the IOS XE release number (for example, 16.7.1, 16.8.1, 3.15.1xbs). Compare against the affected version list: 3.15.1xbs, 3.15.2xbs, 16.7.1, 16.7.1a, 16.7.1b, 16.7.2, 16.7.3, 16.7.4, 16.8.1, 16.8.1a, 16.8.1b, or any version if the 'all versions' note appliesAffected if The installed IOS XE version matches or falls within the affected version ranges
-
Verify IPv6 is enabledRun 'show ipv6 interface brief' to confirm IPv6 is configured and active on any interfacesAffected if IPv6 is enabled on the device (the vulnerability affects IPv6 link-local traffic processing)
-
Monitor for L2 loop symptomsRun 'show interface' and 'show spanning-tree' to check for unusually high traffic counts, CRC errors, or spanning-tree topology changes. Use 'show vlan' and 'show interface switchport' to identify VLANs experiencing traffic drops or loop conditionsAffected if L2 loop indicators are present in any VLAN served by the affected device
The device is affected if it is a Cisco Catalyst 9000 Family Wireless Controller running a vulnerable IOS XE version with IPv6 enabled, and unexpected L2 loops or VLAN traffic anomalies are observed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the Cisco software update (patch) for CVE-2021-34767 to affected Cisco Catalyst 9000 Family Wireless Controllers. Until patched, monitor for unexpected L2 loops and IPv6 traffic anomalies in VLANs served by affected devices.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34767 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-34767 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data