Ios XeOperating system · Cisco

CVE-2020-3429

MEDIUM · 6.5 CVSS v3.1 Published 2020-09-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
A vulnerability in the WPA2 and WPA3 security implementation of Cisco IOS XE Wireless Controller Software for the Cisco Catalyst 9000 Family could allow an unauthenticated, adjacent attacker to cause denial of service (DoS) condition on an affected device. The vulnerability is due to incorrect packet processing during the WPA2 and WPA3 authentication handshake when configured for dot1x or pre-shared key (PSK) authentication key management (AKM) with 802.11r BSS Fast Transition (FT) enabled. An attacker could exploit this vulnerability by sending a crafted authentication packet to an affected device. A successful exploit could cause an affected device to reload, resulting in a 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 confidence

A vulnerability in the WPA2 and WPA3 implementation of Cisco IOS XE Wireless Controller Software for Catalyst 9000 Family allows an unauthenticated, adjacent attacker to cause device reload (DoS) by sending a crafted authentication packet. The flaw exists in packet processing during WPA2/WPA3 handshake when configured with dot1x or PSK AKM and 802.11r BSS Fast Transition (FT) enabled.

MitigationEither update to a patched Cisco IOS XE version, or if 802.11r FT is not required, disable BSS Fast Transition in the wireless controller configuration as an interim workaround.

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 data
Ios XeOperating system
Affected:= 16.12.1s

CVSS 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
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Cisco IOS XE version
    Run 'show version' on the device CLI and locate the IOS XE version number in the output
    Affected if The version matches 16.12.1s or falls within the affected version range
  2. Confirm wireless controller is in use
    Run 'show wireless summary' or 'show controller' to verify the device has Wireless Controller functionality enabled
    Affected if Wireless Controller Software for Catalyst 9000 Family is active
  3. Verify 802.11r BSS Fast Transition is enabled
    Run 'show wireless mobility summary' or 'show run | include ft' to check if Fast Transition is configured on WLANs or wireless profiles
    Affected if 802.11r BSS Fast Transition is enabled in the wireless configuration
  4. Check wireless security AKM mode
    Run 'show wlan summary' and 'show wlan id <num>' to view WLAN security settings, looking for dot1x or PSK authentication key management
    Affected if WLAN is configured with dot1x or PSK AKM mode

A device is affected if it runs a vulnerable IOS XE version AND has wireless controller enabled AND uses dot1x or PSK AKM AND has 802.11r BSS Fast Transition simultaneously configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Either update to a patched Cisco IOS XE version, or if 802.11r FT is not required, disable BSS Fast Transition in the wireless controller configuration as an interim workaround.

Fix this in Ios Xe Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3429 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-3429 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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