Wireless Lan Controller SoftwareOperating system · Cisco
CVE-2015-0679
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-authentication functionality on Cisco Wireless LAN Controller (WLC) devices 7.3(103.8) and 7.4(110.0) allows remote attackers to cause a denial of service (device reload) via a malformed password, aka Bug ID CSCui57980.
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 denial of service vulnerability exists in the web-authentication component of Cisco Wireless LAN Controller devices running versions 7.3(103.8) and 7.4(110.0). Remote attackers can trigger a device reload by submitting a malformed password through the web authentication interface, causing service interruption.
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.3\(103.8\)= 7.4\(110.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
- Adjacent
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:A/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 modelLog into the controller CLI and run 'show inventory' or check the device chassis label to confirm it is a Cisco Wireless LAN Controller (WLC) model.Affected if The device is not a Cisco WLC.
-
Check the software versionLog into the controller CLI and run 'show version' to display the running software version. Compare the version number to the affected versions 7.3(103.8) and 7.4(110.0).Affected if The running version is exactly 7.3(103.8) or exactly 7.4(110.0).
-
Verify web authentication is enabledLog into the controller CLI and run 'show running-config | include web' or access the web interface and navigate to Security > Web Auth to confirm web-based authentication is enabled.Affected if Web authentication is enabled on the controller.
-
Confirm web management interface accessibilityCheck if the web management interface (HTTP/HTTPS on ports 80/443) is reachable from untrusted networks by reviewing the interface bindings with 'show interface summary' or checking the access-list applied to the management interface.Affected if The web interface is accessible from untrusted networks (not restricted by ACLs or VPN).
A user is affected if they are running Cisco WLC software version 7.3(103.8) or 7.4(110.0) with web authentication enabled and the web interface accessible to potential 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 software update that addresses this vulnerability. Until patched, consider restricting web management interface access to trusted networks or disabling web-based authentication if not required.
Fix this in Wireless Lan Controller Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0679 — 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-0679 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