CVE-2020-3390
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 Simple Network Management Protocol (SNMP) trap generation for wireless clients of the Cisco IOS XE Wireless Controller Software for the Cisco Catalyst 9000 Family could allow an unauthenticated, adjacent attacker to cause the device to unexpectedly reload, causing a denial of service (DoS) condition on an affected device. The vulnerability is due to the lack of input validation of the information used to generate an SNMP trap in relation to a wireless client connection. An attacker could exploit this vulnerability by sending an 802.1x packet with crafted parameters during the wireless authentication setup phase of a connection. A successful exploit could allow the attacker to cause the device to reload, causing 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 confidenceA vulnerability in Cisco IOS XE Wireless Controller Software for Catalyst 9000 devices exists due to lack of input validation when generating SNMP traps for wireless client 802.1x authentication. An adjacent, unauthenticated attacker can send crafted 802.1x packets during the wireless authentication phase, causing the device to unexpectedly reload and create a denial of service condition.
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= 16.12.1CVSS 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 software platformRun 'show version' or 'show inventory' to confirm the device is a Cisco Catalyst 9000 series switch running Cisco IOS XE software.Affected if Device is not a Catalyst 9000 series or does not run IOS XE.
-
Check the IOS XE versionRun 'show version' and locate the IOS XE version number in the output. Compare it to the affected version 16.12.1.Affected if The installed IOS XE version is exactly 16.12.1.
-
Verify wireless controller feature is enabledRun 'show wireless controller' or 'show wireless management' to confirm the wireless controller functionality is active on the device.Affected if Wireless controller feature is not enabled.
-
Confirm 802.1x authentication is configuredRun 'show run | include dot1x' or 'show authentication session' to check if 802.1x authentication is configured for wireless clients.Affected if 802.1x authentication is not configured for wireless clients.
-
Check SNMP configuration for wireless authentication trapsRun 'show snmp trap' or 'show run | include snmp' to verify SNMP is configured and check if wireless authentication-related traps are enabled.Affected if SNMP is not configured or wireless authentication traps are not enabled.
The device is affected if it is a Catalyst 9000 running IOS XE version 16.12.1 with the wireless controller feature enabled, 802.1x authentication configured for wireless clients, and SNMP traps for wireless authentication are active.
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 patch for CVE-2020-3390 when available from Cisco. Until patched, consider network segmentation to limit adjacent attacker access to the wireless network and 802.1x authentication infrastructure.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3390 — 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-2020-3390 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