Wireless Lan ControllerApplication · Cisco
CVE-2019-1800
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 · uneditedA vulnerability in the handling of Inter-Access Point Protocol (IAPP) messages by Cisco Wireless LAN Controller (WLC) Software could allow an unauthenticated, adjacent attacker to cause a denial of service (DoS) condition. The vulnerability exist because the software improperly validates input on fields within IAPP messages. An attacker could exploit the vulnerability by sending malicious IAPP messages to an affected device. A successful exploit could allow the attacker to cause the Cisco WLC Software to reload, resulting in a DoS condition. Software versions prior to 8.2.170.0, 8.5.150.0, and 8.8.100.0 are affected.
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 vulnerability exists in Cisco Wireless LAN Controller (WLC) Software where improper validation of input fields within Inter-Access Point Protocol (IAPP) messages allows an unauthenticated, adjacent attacker to send malicious IAPP messages that cause 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 ControllerApplication
< 8.2.170.0
Wireless Lan Controller SoftwareOperating system
>= 8.3, < 8.5.150.0>= 8.6, < 8.8.100.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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 modelRun 'show inventory' or 'show controller' command to confirm the hardware is a Cisco Wireless LAN Controller (model numbers typically include AIR-CT, Cisco 5500 Series, Cisco 8500 Series, etc.)Affected if The device is a Cisco Wireless LAN Controller
-
Check the software versionRun 'show version' on the WLC CLI to retrieve the installed software version number (e.g., 8.2.100.0, 8.5.120.0)Affected if The installed version falls into any of these ranges: < 8.2.170.0, >= 8.3 and < 8.5.150.0, or >= 8.6 and < 8.8.100.0
-
Determine if IAPP is in useRun 'show ap config general' or 'show run | include iapp' to check if Inter-Access Point Protocol (IAPP) is enabled on the controller. IAPP is used for AP-to-AP communication in mobility groups.Affected if IAPP is enabled and the version is in the affected range listed above
-
Assess network accessibilityReview the wireless network topology to determine if the WLC and its associated APs are exposed to adjacent (untrusted) network segments. This is a precondition for the adjacent attacker to send malicious IAPP messages.Affected if The wireless infrastructure is accessible to unauthenticated adjacent attackers and the version is affected
You are affected if your Cisco WLC runs a software version less than 8.2.170.0, between 8.3 and 8.5.149.0, or between 8.6 and 8.8.99.0, and IAPP is enabled with potential adjacent network access.
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 data8.2.170.08.5.150.08.8.100.0
Upgrade Cisco WLC Software to version 8.2.170.0, 8.5.150.0, or 8.8.100.0 or later. If immediate upgrade is not possible, consider network segmentation to limit adjacent attacker access to the wireless infrastructure.
Fix this in Wireless Lan Controller
Scoped from the published advisory
- Consultation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1800 — 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-2019-1800 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