CVE-2016-1460
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 · uneditedCisco Wireless LAN Controller (WLC) devices 7.4(121.0) and 8.0(0.30220.385) allow remote attackers to cause a denial of service via crafted wireless management frames, aka Bug ID CSCun92979.
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 confidenceCisco Wireless LAN Controller devices versions 7.4(121.0) and 8.0(0.30220.385) are vulnerable to a denial-of-service attack via crafted wireless management frames. A remote attacker can send specially crafted frames to the WLC, causing the device to become unresponsive or crash, disrupting wireless network services.
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= 7.4.121.0= 8.0.0.30220.385CVSS 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.
-
Verify device is a Cisco Wireless LAN ControllerAccess the WLC CLI and run 'show inventory' or check the GUI under Monitor > Summary to confirm the device model is a Cisco Wireless LAN Controller (WLC)Affected if Device is not a Cisco WLC - this CVE does not apply to other Cisco products
-
Check WLC firmware version via CLILog into the WLC CLI and run the command 'show version' to display the installed software versionAffected if The displayed version matches 7.4.121.0 or 8.0.0.30220.385 exactly
-
Check WLC firmware version via GUILog into the WLC web interface and navigate to Monitor > Summary or Controller > Summary to view the Software Version fieldAffected if The displayed version matches 7.4.121.0 or 8.0.0.30220.385 exactly
-
Confirm wireless management frame processing is enabledThis vulnerability is triggered by receiving crafted wireless management frames. By default, WLC devices accept management frames on configured WLANs. No specific feature toggle needs to be enabled for the device to be vulnerable.Affected if The WLC has at least one WLAN configured and is actively processing wireless traffic - the device is vulnerable to the attack vector when running an affected version
The environment is affected if the Cisco Wireless LAN Controller is running exactly version 7.4.121.0 or version 8.0.0.30220.385 and has an active WLAN configuration that accepts wireless management frames.
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 corresponding Cisco firmware update/patch for the affected WLC versions. If immediate patching is not feasible, consider network segmentation to limit exposure of management interfaces and implement rate limiting on wireless management frames as compensating controls.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1460 — 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-1460 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