CVE-2022-20856
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 the processing of Control and Provisioning of Wireless Access Points (CAPWAP) Mobility messages in Cisco IOS XE Wireless Controller Software for the Catalyst 9000 Family could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to a logic error and improper management of resources related to the handling of CAPWAP Mobility messages. An attacker could exploit this vulnerability by sending crafted CAPWAP Mobility packets to an affected device. A successful exploit could allow the attacker to exhaust resources on the affected device. This would cause the 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 confidenceA logic error in Cisco IOS XE Wireless Controller Software for Catalyst 9000 Family causes improper resource management when processing CAPWAP Mobility messages. An unauthenticated remote attacker can send crafted CAPWAP Mobility packets to exhaust device resources, forcing the affected device to reload and causing denial of service.
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= 17.3.4cCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and software platformRun 'show version' or 'show inventory' to confirm the device is a Cisco Catalyst 9000 series switch and is running IOS XE softwareAffected if Device is not a Catalyst 9000 family member or does not run IOS XE
-
Check IOS XE versionRun 'show version' and locate the IOS XE software version number (for example, 'Version 17.3.4c')Affected if Version is exactly 17.3.4c
-
Verify Wireless Controller feature is enabledRun 'show wireless mobility summary' or 'show running-config | include wireless' to check if wireless controller functionality is configuredAffected if Wireless controller feature is enabled and CAPWAP is in use
-
Confirm CAPWAP listen interfaces are accessibleRun 'show wireless management interface' to identify which interface(s) accept CAPWAP connections, then determine if these are exposed to untrusted networksAffected if CAPWAP management interface is reachable from untrusted networks
If the device is a Catalyst 9000 running IOS XE version 17.3.4c with wireless controller enabled and CAPWAP interfaces exposed to untrusted networks, the environment is affected by this CVE.
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.
dbcve · scopedApply the vendor-provided patch when available. Until then, consider network segmentation or ACLs to limit CAPWAP traffic to trusted sources, and monitor for unusual CAPWAP traffic patterns.
Upgrade to the fixed IOS XE release for 17.3.x as specified in the Cisco security advisory for CVE-2022-20856 (check Cisco.com for the exact fixed version number)
- 1. Identify the current Cisco IOS XE Wireless Controller Software version running on the affected Catalyst 9000 Family device using 'show version' command
- 2. Access Cisco.com and navigate to the Cisco Security Advisories page for CVE-2022-20856 to obtain the specific fixed release information
- 3. Download the fixed IOS XE software version from Cisco's software download center
- 4. Upload the new software image to the device's flash storage
- 5. Configure boot system to point to the new image: 'boot system <flash:/new-image-name>'
- 6. Save configuration: 'write memory'
- 7. Reload the device to apply the new software: 'reload'
- 8. After reboot, verify the new version is running: 'show version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20856 — 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-2022-20856 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