Wireless Lan Controller SoftwareOperating system · Cisco
CVE-2014-0707
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, 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 CSCuf80681.
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, 7.3, and 7.4 prior to 7.4.110.0 are vulnerable to a denial of service attack. A remote attacker can send a specially crafted 802.11 Ethernet frame to the WLC, causing the device to unexpectedly restart, disrupting all connected wireless clients.
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.
-
Identify the device as a Cisco Wireless LAN ControllerRun 'show inventory' or 'show version' on the device CLI, or check the device web interface system informationAffected if The device is a Cisco WLC (model numbers like 2500, 5500, 8500 series, or Airespace AS-5500 series)
-
Determine the software version running on the WLCExecute 'show version' on the WLC CLI and locate the version string (for example: 7.2.x, 7.3.x, or 7.4.x)Affected if The displayed version is 7.2, 7.2.103.0, 7.2.110.0, 7.3, 7.3.101.0, 7.4.100.0, or 7.4.100.60, or any version in 7.2.x, 7.3.x, or 7.4.x prior to 7.4.110.0
-
Verify if the WLC is processing 802.11 management trafficCheck the WLC configuration with 'show running-config' or the web interface under Wireless > Access Points to confirm WLANs are enabled and the controller is accepting client associationsAffected if The WLC has WLANs configured and is actively processing or configured to process 802.11 wireless traffic (this is the default operational state for a WLC)
If the device is a Cisco Wireless LAN Controller running software version 7.2.x, 7.3.x, or any 7.4.x version prior to 7.4.110.0, and it is processing 802.11 traffic, 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.
From vendor dataUpgrade Cisco WLC firmware to version 7.4.110.0 or later. If immediate upgrade is not possible, consider network segmentation to limit exposure and implement monitoring for signs of anomalous frame traffic.
Fix this in Wireless Lan Controller Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0707 — 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-0707 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