dbcve.org
Wireless Lan Controller SoftwareOperating system · Cisco

CVE-2015-6302

MEDIUM · 5.0 CVSS v2.0 Published 2015-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
The RADIUS functionality on Cisco Wireless LAN Controller (WLC) devices with software 7.0(250.0) and 7.0(252.0) allows remote attackers to disconnect arbitrary sessions via crafted Disconnect-Request UDP packets, aka Bug ID CSCuw29419.

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 · moderate confidence

The vulnerability exists in the RADIUS implementation on Cisco Wireless LAN Controller devices running software versions 7.0(250.0) and 7.0(252.0). Attackers can send specially crafted Disconnect-Request UDP packets to the RADIUS service port (UDP 3799) to forcibly terminate arbitrary wireless user sessions without authentication.

MitigationUpgrade Cisco WLC software to a version beyond 7.0(252.0) that includes the fix for CSCuw29419. If immediate patching is not possible, consider filtering Disconnect-Request packets at network boundaries or implementing additional access controls on the RADIUS UDP port.

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
Affected:= 7.0.250.0= 7.0.252.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
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 checks

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

  1. Identify device model and confirm it is a Cisco Wireless LAN Controller
    Run 'show inventory' or 'show version' on the WLC CLI to confirm the device is a Cisco Wireless LAN Controller
    Affected if Device is not a Cisco Wireless LAN Controller (not affected)
  2. Check the exact software version installed
    Run 'show version' on the WLC CLI and locate the software version string (e.g., 7.0.250.0 or 7.0.252.0)
    Affected if Version is exactly 7.0.250.0 or 7.0.252.0 (these are the affected versions)
  3. Verify RADIUS is configured on the controller
    Run 'show radius summary' or 'show radius auth statistics' to check if RADIUS servers are defined and active
    Affected if RADIUS is not configured (the vulnerability requires RADIUS to be in use)
  4. Confirm UDP port 3799 is accessible
    Check if the RADIUS Disconnect-Request port (UDP 3799) is open and reachable from network segments using 'show network' or port scanning from an external host
    Affected if UDP port 3799 is exposed to untrusted network segments

You are affected if you are running exactly version 7.0.250.0 or 7.0.252.0 on a Cisco WLC with RADIUS enabled and UDP port 3799 is accessible.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco WLC software to a version beyond 7.0(252.0) that includes the fix for CSCuw29419. If immediate patching is not possible, consider filtering Disconnect-Request packets at network boundaries or implementing additional access controls on the RADIUS UDP port.

Fix this in Wireless Lan Controller Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Check whether your project pulls in CVE-2015-6302 — 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-6302 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