CVE-2015-0723
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 wireless web-authentication subsystem on Cisco Wireless LAN Controller (WLC) devices 7.5.x and 7.6.x before 7.6.120 allows remote attackers to cause a denial of service (process crash and device restart) via a crafted value, aka Bug ID CSCum03269.
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 wireless web-authentication subsystem of Cisco Wireless LAN Controller devices running versions 7.5.x and 7.6.x before 7.6.120. Remote attackers can send a crafted value that causes a process crash, leading to device restart and service disruption.
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= 7.5.102.0= 7.5.102.11= 7.6.100.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
- 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.
-
Determine the installed Cisco WLC software versionLog into the Cisco Wireless LAN Controller CLI and run the command 'show version' to display the software version information. Alternatively, access the WLC web interface and navigate to Monitor > Controller Summary to view the running software version.Affected if The displayed version matches 7.5.x or 7.6.x versions prior to 7.6.120 (for example, 7.5.102.0, 7.5.102.11, or 7.6.100.0).
-
Confirm wireless web-authentication is enabledIn the WLC CLI, run 'show wlan summary' to list configured WLANs, then check the security settings of each WLAN with 'show wlan <id>' to see if web authentication is configured. In the web interface, navigate to WLANs > WLAN ID > Security > Layer 3 Security to verify web authentication is enabled.Affected if Web authentication (centralized or local) is enabled on any WLAN profile, as the vulnerability exists in the web-authentication subsystem.
-
Verify the process handling web-authenticationIn the WLC CLI, use 'show process cpu history' or 'show process memory' to observe the web-auth service process. Check for any existing crash logs with 'show crashdump' to see if the webauth process has previously crashed.Affected if The device shows signs of unexpected process restarts or crashes related to the web-authentication process, indicating possible exploitation.
The device is affected if it runs Cisco WLC software version 7.5.x or 7.6.x prior to 7.6.120 and has wireless web-authentication enabled, as the vulnerability specifically targets this subsystem.
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 vendor patch by upgrading to Cisco WLC version 7.6.120 or later (or the latest supported release). If immediate patching is not feasible, restrict access to the web-authentication interface via network segmentation or ACLs.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0723 — 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-0723 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