Wireless Lan Controller SoftwareOperating system · Cisco
CVE-2014-0706
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.2 before 7.2.115.2, 7.3, and 7.4 before 7.4.110.0 allow remote attackers to cause a denial of service (device restart) via a crafted 802.11 Ethernet frame, aka Bug ID CSCue87929.
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 running versions 7.2 before 7.2.115.2, 7.3, and 7.4 before 7.4.110.0 are vulnerable to a denial of service attack. Remote attackers can send a crafted 802.11 Ethernet frame that causes the WLC device to restart, 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
Wireless Lan Controller SoftwareOperating system
= 7.2= 7.2.103.0= 7.2.110.0= 7.3= 7.3.101.0= 7.4.100.0= 7.4.100.60
Wireless Lan ControllerHardware / appliance
all versionsCVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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.
-
Determine WLC software versionLog into the WLC CLI and run 'show version' or use the GUI under Monitor > Statistics > Software Version to identify the installed Cisco Wireless LAN Controller software version.Affected if The displayed version falls within 7.2 before 7.2.115.2, any 7.3.x version, or 7.4 before 7.4.110.0.
-
Confirm 802.11 radio is enabledIn the WLC CLI, run 'show 802.11a status' and 'show 802.11b status' to check if the 802.11a/b/g radio interfaces are enabled.Affected if At least one 802.11 radio is enabled, as the vulnerability is triggered by crafted 802.11 Ethernet frames.
-
Verify management interface accessibilityFrom a management station, attempt to reach the WLC management IP on ports 80/443 or use 'show mgmtuser' to review allowed management access methods.Affected if The WLC management interface is accessible from untrusted networks, allowing remote attackers to send the malicious frames.
A Cisco WLC is affected if it runs software version 7.2 prior to 7.2.115.2, any 7.3.x version, or 7.4 prior to 7.4.110, and has 802.11 radios enabled with network accessibility for remote attackers.
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 dataUpgrade Cisco WLC firmware to version 7.2.115.2 or later for the 7.2 branch, or 7.4.110.0 or later for the 7.4 branch. Schedule maintenance window and ensure configuration backup before upgrading.
Fix this in Wireless Lan Controller Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation3.0 h
- Testing3.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0706 — 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-2014-0706 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