Aironet Access Point SoftwareApplication · Cisco
CVE-2016-6361
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 · uneditedThe Aggregated MAC Protocol Data Unit (AMPDU) implementation on Cisco Aironet 1800, 2800, and 3800 devices with software before 8.2.121.0 and 8.3.x before 8.3.102.0 allows remote attackers to cause a denial of service (device reload) via a crafted AMPDU header, aka Bug ID CSCuz56288.
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 the AMPDU (Aggregated MAC Protocol Data Unit) handling code in Cisco Aironet 1800, 2800, and 3800 series wireless access points allows remote attackers to send specially crafted AMPDU frames that trigger a device reload, 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
Aironet Access Point SoftwareApplication
= 8.1\(15.14\)= 8.1\(112.3\)= 8.1\(112.4\)= 8.1\(131.0\)= 8.2\(100.0\)= 8.2\(102.43\)= 8.3.0CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Cisco Aironet access point modelRun 'show version' or check the AP physical label to confirm it is an 1800, 2800, or 3800 series access pointAffected if The device is NOT one of these three model series - the vulnerability does not apply
-
Check the installed Cisco Aironet software versionExecute 'show version' on the AP CLI and locate the version string (for example, 8.1(15.14), 8.2(100.0), or 8.3.0)Affected if The installed version matches exactly 8.1(15.14), 8.1(112.3), 8.1(112.4), 8.1(131.0), 8.2(100.0), 8.2(102.43), or 8.3.0
-
Confirm AMPDU processing is enabledRun 'show wireless client summary' or check the radio configuration with 'show run | include ampdu' to verify the AP is processing AMPDU framesAffected if AMPDU is disabled on all radios - the crafted frames would not trigger the vulnerability in this case; however, AMPDU is typically enabled by default on these APs for 802.11n/802.11ac operation
You are affected if you have a Cisco Aironet 1800, 2800, or 3800 series AP running software version 8.1(15.14), 8.1(112.3), 8.1(112.4), 8.1(131.0), 8.2(100.0), 8.2(102.43), or 8.3.0 with AMPDU processing enabled on any radio interface.
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 Cisco software updates 8.2.121.0 or later for 8.2.x releases, or 8.3.102.0 or later for 8.3.x releases. Prior to deployment, verify current firmware version and schedule a maintenance window.
Fix this in Aironet Access Point Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6361 — 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-2016-6361 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