Wireless Lan Controller SoftwareOperating system · Cisco
CVE-2013-1141
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 mDNS snooping functionality on Cisco Wireless LAN Controller (WLC) devices with software 7.4.1.54 and earlier does not properly manage buffers, which allows remote authenticated users to cause a denial of service (device reload) via crafted mDNS packets, aka Bug ID CSCue04153.
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 buffer management vulnerability exists in the mDNS snooping feature of Cisco Wireless LAN Controller devices running software 7.4.1.54 and earlier. Remote authenticated users can exploit this by sending specially crafted mDNS packets, triggering a buffer handling error that causes the device to reload, resulting in denial of service.
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.4.1.54= 3.0= 3.2= 3.2.116.21= 4.0= 4.0.108= 4.0.155.0= 4.0.155.5= 4.0.179.8= 4.0.179.11= 4.0.196= 4.0.206.0
Wireless Lan ControllerHardware / appliance
all versionsCVSS 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.
-
Check the WLC software versionRun 'show version' or 'show run' on the Cisco WLC CLI and locate the software version numberAffected if The version is 7.4.1.54 or earlier, or matches one of these: 3.0, 3.2, 3.2.116.21, 4.0, 4.0.108, 4.0.155.0, 4.0.155.5, 4.0.179.8, 4.0.179.11, 4.0.196, or 4.0.206.0
-
Confirm mDNS snooping is enabledRun 'show mdns snoop detail' or 'show running-config | include mdns' to check if mDNS snooping feature is activeAffected if mDNS snooping is enabled (the feature must be running for the vulnerability to be exploitable)
-
Verify the device is a Cisco Wireless LAN ControllerRun 'show inventory' or 'show controller' to identify the hardware platformAffected if The device is any model of Cisco Wireless LAN Controller (all hardware versions are affected when running vulnerable software)
You are affected if your WLC runs software version 7.4.1.54 or earlier (or one of the specific versions listed) AND mDNS snooping is enabled on the device.
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 version later than 7.4.1.54. If immediate upgrading is not feasible, consider disabling mDNS snooping if the feature is not required, and ensure network access controls limit exposure to authenticated attackers.
Fix this in Wireless Lan Controller Software
Scoped from the published advisory
- Consultation4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1141 — 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-2013-1141 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