Small Business Wireless Access PpointsHardware / appliance · Cisco
CVE-2013-1131
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 Small Business Wireless Access Points WAP200, WAP2000, WAP200E, and WET200 allow remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted SSID that is not properly handled during a site survey, aka Bug IDs CSCua86182, CSCua91196, CSCud36155, and CSCua86190.
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 confidenceThe vulnerability exists in Cisco Small Business Wireless Access Points (WAP200, WAP2000, WAP200E, and WET200) where a crafted SSID is not properly handled during site survey operations. A remote attacker can cause denial of service or potentially achieve unspecified other impact by transmitting a specially crafted SSID that triggers improper handling in the device firmware.
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
Small Business Wireless Access PpointsHardware / appliance
= wap200= wap200e= wap2000= wet200CVSS 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Complete
AV:A/AC:M/Au:N/C:N/I:P/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.
-
Identify the device modelAccess the device web interface (typically http://192.168.1.245) or check the physical device label to confirm the exact model number (WAP200, WAP200E, WAP2000, or WET200)Affected if The device model is one of: WAP200, WAP200E, WAP2000, or WET200
-
Check the firmware versionLog into the device admin console and navigate to the Status or Administration section to view the firmware versionAffected if The installed firmware version has not been updated to address this vulnerability (compare your version to any available Cisco firmware releases for these models)
-
Determine if site survey feature is accessibleNavigate to the wireless settings or diagnostics section of the device admin interface to locate the site survey functionAffected if The device has an active site survey feature that can be invoked
-
Verify wireless radio is enabledCheck the wireless configuration page to confirm the radio is turned on and the device is operating as an access pointAffected if The wireless radio is enabled and the device is broadcasting
A user is affected if they own one of the listed models (WAP200, WAP200E, WAP2000, or WET200) and are using the device with its wireless functionality enabled, particularly when site survey operations are performed.
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 dataIf available, apply vendor firmware updates from Cisco. Otherwise, restrict physical and wireless proximity to untrusted networks and monitor for device instability during site surveys.
Fix this in Small Business Wireless Access Ppoints
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1131 — 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-1131 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