Wireless Lan Controller SoftwareOperating system · Cisco
CVE-2015-4215
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 with software 7.5(102.0) and 7.6(1.62) allow remote attackers to cause a denial of service (device crash) by triggering an exception during attempted forwarding of unspecified IPv6 packets to a non-IPv6 device, aka Bug ID CSCuj01046.
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 software versions 7.5(102.0) and 7.6(1.62) contain a denial-of-service vulnerability in their IPv6 packet forwarding logic. When the device attempts to forward certain unspecified IPv6 packets to a non-IPv6 device, an unhandled exception is triggered, causing the controller to crash.
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.5.102.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.
-
Confirm device is a Cisco Wireless LAN ControllerLog into the device CLI and run 'show inventory' or check the device model via 'show version' to verify it is a Cisco WLC hardware platformAffected if The device is not a Cisco Wireless LAN Controller, then this CVE does not apply
-
Check the running software versionExecute 'show version' in the WLC CLI and locate the firmware version string (e.g., 7.5.102.0 or 7.6.1.62)Affected if The installed version is exactly 7.5.102.0 or 7.6.1.62 (the versions listed in the affected products)
-
Verify IPv6 is enabled on the controllerRun 'show ipv6 status' or 'show run config' and look for IPv6-related interface configurations or IPv6 forwarding settingsAffected if IPv6 is enabled and the device is configured to forward IPv6 traffic
-
Check for downstream non-IPv6 network segmentsReview the WLC interface mappings and AP group configurations using 'show interface summary' and 'show ap config general' to identify if any WLANs or interfaces are mapped to segments that contain non-IPv6 devicesAffected if The controller has WLANs or interfaces serving devices that do not support IPv6, and IPv6 traffic can reach those segments
You are affected if you are running Cisco WLC software version 7.5.102.0 or 7.6.1.62, IPv6 is enabled, and your network includes non-IPv6 client segments that can receive forwarded IPv6 traffic.
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 software to a patched version beyond 7.5(102.0) and 7.6(1.62) per Cisco's release notes, or contact Cisco TAC for the specific fixed release. As a workaround, consider filtering or blocking IPv6 traffic to non-IPv6 segments until the upgrade can be performed.
Fix this in Wireless Lan Controller Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.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 $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4215 — 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-4215 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