Wireless Lan Controller SoftwareOperating system · Cisco
CVE-2015-6341
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 Web Management GUI on Cisco Wireless LAN Controller (WLC) devices with software 7.4(140.0) and 8.0(120.0) allows remote attackers to cause a denial of service (client disconnection) via unspecified vectors, aka Bug ID CSCuw10610.
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 exists in the Web Management GUI of Cisco Wireless LAN Controller (WLC) devices running software versions 7.4(140.0) and 8.0(120.0). Remote attackers can exploit unspecified vectors in the web interface to cause a denial of service condition, resulting in wireless client disconnection.
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.4.140.0= 8.0.120.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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 Cisco WLC device and software versionAccess the WLC CLI and run 'show version' or log into the Web Management GUI to view the software version displayed on the login page or dashboardAffected if The displayed software version is exactly 7.4.140.0 or exactly 8.0.120.0
-
Confirm the Web Management GUI is enabledIn the WLC CLI, run 'show management' or access the GUI under Controller > Management > HTTP/HTTPS to verify the web interface is enabledAffected if HTTP or HTTPS management access is enabled on the WLC
-
Verify network exposure of management interfaceCheck the WLC management interface configuration using 'show interface' or by reviewing the GUI under Controller > Interfaces to determine if the management IP is reachable from untrusted networksAffected if The WLC management interface is accessible from outside the trusted network (e.g., directly via public IP or without proper ACL filtering)
A user is affected if they are running exactly version 7.4.140.0 or 8.0.120.0 AND the Web Management GUI is enabled and reachable from network 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 dataApply the Cisco patch for bug ID CSCuw10610 (upgrade to a patched WLC software version). As an interim measure, restrict access to the WLC Web Management GUI using ACLs or VPNs, and disable the GUI if not required.
Fix this in Wireless Lan Controller Software
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.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 $3,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6341 — 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-2015-6341 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