Wireless Lan Controller SoftwareOperating system · Cisco
CVE-2011-1613
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 · uneditedUnspecified vulnerability in Cisco Wireless LAN Controller (WLC) software 6.0 before 6.0.200.0, 7.0 before 7.0.98.216, and 7.0.1xx before 7.0.112.0 allows remote attackers to cause a denial of service (device reload) via a sequence of ICMP packets, aka Bug ID CSCth74426.
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 confidenceDenial of service vulnerability in Cisco Wireless LAN Controller software allows unauthenticated remote attackers to cause device reload by sending a specific sequence of ICMP packets. The vulnerability affects versions 6.0 before 6.0.200.0, 7.0 before 7.0.98.216, and 7.0.1xx before 7.0.112.0.
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
= 6.0.182.0= 6.0.188.0= 6.0.196.0= 6.0.199.0= 6.0.199.4= 7.0.98.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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/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.
-
Check the Cisco WLC software version via CLIConnect to the WLC controller CLI and run the command: `show version` or `show run-config | include version`. Locate the line showing the software version (for example: 6.0.188.0 or 7.0.98.0).Affected if The installed version matches 6.0.182.0, 6.0.188.0, 6.0.196.0, 6.0.199.0, 6.0.199.4, 7.0.98.0, or any version in the ranges 6.0 before 6.0.200.0, 7.0 before 7.0.98.216, or 7.0.1xx before 7.0.112.0.
-
Verify the WLC management interface is reachable via ICMPFrom an external host, attempt to ping the WLC management IP address. Also check any network diagrams or firewall rules to confirm ICMP (ICMP type 8/0) traffic is permitted toward the WLC device.Affected if The WLC responds to ICMP echo requests from untrusted networks, meaning an unauthenticated attacker can send the malicious ICMP packet sequence directly to the device.
-
Confirm the WLC is in production and handling trafficRun `show client summary` or `show ap summary` on the WLC CLI to verify the controller is actively managing access points and clients.Affected if The device is actively deployed and processing wireless traffic, making a reload caused by the ICMP attack disruptive to operations.
If the installed Cisco WLC software version falls within the affected ranges and the device is reachable via ICMP from an untrusted network, the environment is vulnerable to CVE-2011-1613 and could be forced to reload via malicious ICMP packets.
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 version 6.0.200.0, 7.0.98.216, or 7.0.112.0 or later per the affected version branch. Consider network-level ICMP traffic filtering as an interim control if immediate upgrade is not feasible.
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
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-2011-1613 — 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-2011-1613 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