dbcve.org
Wireless Lan Controller SoftwareApplication · Cisco

CVE-2015-6314

CRITICAL · 9.8 CVSS v3.0 Published 2016-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Cisco Wireless LAN Controller (WLC) devices with software 7.6.x, 8.0 before 8.0.121.0, and 8.1 before 8.1.131.0 allow remote attackers to change configuration settings via unspecified vectors, aka Bug ID CSCuw06153.

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 confidence

Cisco Wireless LAN Controller devices running software versions 7.6.x, 8.0 before 8.0.121.0, and 8.1 before 8.1.131.0 contain a vulnerability allowing remote attackers to change configuration settings without authentication. This critical flaw enables unauthorized modification of wireless network parameters, potentially disrupting services or enabling further attacks.

MitigationUpgrade Cisco WLC software to version 8.0.121.0 or 8.1.131.0 or later. If immediate patching is not feasible, restrict management interface access to trusted networks and monitor for unauthorized configuration changes.

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 SoftwareApplication
Affected:= 8.0.72.140= 8.0_base= 8.1.0= 8.1.104.37= 8.1.111.0= 8.1.122.0

CVSS 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Log into the Cisco Wireless LAN Controller and retrieve the device model information using the 'show inventory' or 'show version' command from the CLI.
    Affected if The device is not a Cisco Wireless LAN Controller (WLC)
  2. Retrieve the software version
    Execute the 'show version' command on the Cisco WLC CLI to display the running software version. Look for the version number in the output.
    Affected if Unable to retrieve the software version from the device
  3. Compare version against affected ranges
    Examine the version number from step 2. Check if it matches 7.6.x, or falls before 8.0.121.0, or falls before 8.1.131.0. Also compare directly against these specific versions if shown: 8.0.72.140, 8.0_base, 8.1.0, 8.1.104.37, 8.1.111.0, 8.1.122.0.
    Affected if The running software version is 7.6.x, or 8.0.x before 8.0.121.0, or 8.1.x before 8.1.131.0
  4. Verify management access exposure
    Check the management interface configuration using 'show network' or 'show run-config' commands to determine if the management VLAN/interface is accessible from untrusted networks.
    Affected if The management interface is accessible from untrusted or external networks (not restricted to trusted management VLANs)
  5. Review recent configuration changes
    Use 'show run-config' and check the configuration change history or logs (if available) for unauthorized or unexpected changes to wireless network parameters.
    Affected if Configuration changes exist that were not initiated by authorized administrators

The environment is affected if the Cisco WLC is running software version 7.6.x, 8.0 before 8.0.121.0, or 8.1 before 8.1.131.0, and the management interface is exposed to untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco WLC software to version 8.0.121.0 or 8.1.131.0 or later. If immediate patching is not feasible, restrict management interface access to trusted networks and monitor for unauthorized configuration changes.

Recommended fix High confidence

Upgrade to WLC 8.0.121.0 or later (8.0.x branch), or 8.1.131.0 or later (8.1.x branch), or latest 8.x stable release

  1. 1. Back up the current Wireless LAN Controller configuration via the Web UI (Commands > Backup > Backup Configuration) or CLI (save config)
  2. 2. Review the Cisco WLC 8.0 and 8.1 release notes for the target fixed version to verify compatibility with your hardware model
  3. 3. Download the fixed software version (8.0.121.0 or later for 8.0.x branch, or 8.1.131.0 or later for 8.1.x branch) from Cisco.com software downloads
  4. 4. If upgrading major versions (e.g., from 8.0.x to 8.1.x), first upgrade to an intermediate compatible version as documented in Cisco's upgrade path matrix
  5. 5. Upload the new firmware image to the WLC via Web UI (Management > Software Update) or CLI (transfer download)
  6. 6. Reboot the Wireless LAN Controller to apply the new software version
  7. 7. After reboot, verify the new software version is running: check via Web UI or CLI (show sysinfo)
  8. 8. Restore the configuration if needed and verify wireless network operation
Caveat Review Cisco release notes for any config changes between your current version and target version; some legacy APs may require compatibility mode settings after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

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
11.0 hours of engineering $1,950
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6314 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-6314 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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