AireosOperating system · Cisco

CVE-2016-1362

HIGH · 7.5 CVSS v3.0 Published 2016-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Cisco AireOS 4.1 through 7.4.120.0, 7.5.x, and 7.6.100.0 on Wireless LAN Controller (WLC) devices allows remote attackers to cause a denial of service (device reload) via a crafted HTTP request, aka Bug ID CSCun86747.

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 confidence

A denial of service vulnerability exists in Cisco AireOS Wireless LAN Controller firmware versions 4.1 through 7.4.120.0, 7.5.x, and 7.6.100.0. Remote unauthenticated attackers can send a crafted HTTP request to the device management interface, causing the WLC to reload unexpectedly. This results in disruption of wireless network services for all connected clients.

MitigationApply the relevant Cisco security patch for this vulnerability (refer to Cisco bug ID CSCun86747). Until patched, restrict management interface access to trusted networks using ACLs or VPNs, and monitor for unusual HTTP traffic patterns.

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
AireosOperating system
Affected:= 4.1_base= 7.4= 7.5_base= 7.6

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/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 checks

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

  1. Retrieve the installed Cisco AireOS firmware version
    Log into the WLC CLI and run the command 'show version' or access the web interface and check the Dashboard/Controller Summary page for the software version
    Affected if The displayed version falls within 4.1 through 7.4.120.0, any 7.5.x version, or 7.6.100.0
  2. Verify the management interface is enabled and accessible
    Check WLC configuration via 'show management' CLI command or review the web interface under Controller > Management > HTTP/HTTPS to confirm the management web server is enabled
    Affected if HTTP or HTTPS management access is enabled, exposing the interface to network traffic
  3. Confirm network exposure of the management interface
    Review access control lists and interface bindings using 'show run-config' or check which interfaces have management IP addresses assigned, particularly looking at the AP-manager and management VLANs
    Affected if The management interface IP is reachable from untrusted networks or the management VLAN is not properly segmented
  4. Identify any existing ACLs filtering management traffic
    Run 'show acl summary' or review the management access list configuration to determine if HTTP/HTTPS traffic to the WLC is restricted
    Affected if No ACLs are applied to block or restrict management interface access, leaving it open to unauthenticated requests

You are affected if your Cisco AireOS version is 4.1 through 7.4.120.0, 7.5.x, or 7.6.100.0 AND the management interface is network-accessible without restriction.

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

Apply the relevant Cisco security patch for this vulnerability (refer to Cisco bug ID CSCun86747). Until patched, restrict management interface access to trusted networks using ACLs or VPNs, and monitor for unusual HTTP traffic patterns.

Fix this in Aireos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1362 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1362 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