dbcve.org
Wireless Lan Controller SoftwareOperating system · Cisco

CVE-2007-4011

HIGH · 7.1 CVSS v2.0 Published 2007-07-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/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 4100 and 4400, Airespace 4000, and Catalyst 6500 and 3750 Wireless LAN Controller (WLC) software before 3.2 20070727, 4.0 before 20070727, and 4.1 before 4.1.180.0 allows remote attackers to cause a denial of service (traffic amplification or ARP storm) via a crafted unicast ARP request that (1) has a destination MAC address unknown to the Layer-2 infrastructure, aka CSCsj69233; or (2) occurs during Layer-3 roaming across IP subnets, aka CSCsj70841.

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

This vulnerability in Cisco Wireless LAN Controllers allows remote attackers to cause denial of service by sending crafted unicast ARP requests that trigger traffic amplification or ARP storms. The attack exploits either (1) ARP requests with destination MAC addresses unknown to the Layer-2 infrastructure, or (2) conditions during Layer-3 roaming across IP subnets, leading to network flooding.

MitigationUpgrade Cisco WLC software to version 3.2 (post-20070727), 4.0 (post-20070727), or 4.1.180.0 or later to patch this vulnerability.

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
Affected:= 3.2= 3.2.116.21= 4.0= 4.0.155.0= 4.1

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
M
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:M/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 checks

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

  1. Identify Cisco WLC software installation
    Log into the wireless controller CLI and run 'show version' or access the web interface to view the software version. On network infrastructure devices, check for Cisco WLC processes or management interfaces.
    Affected if Cisco Wireless LAN Controller software is running on the device
  2. Determine the exact WLC software version
    Execute 'show version' on the Cisco WLC CLI. Look for a version string such as 3.2, 3.2.116.21, 4.0, 4.0.155.0, or 4.1.
    Affected if The installed version matches exactly 3.2, 3.2.116.21, 4.0, 4.0.155.0, or 4.1
  3. Verify ARP processing is enabled
    On the WLC CLI, run 'show arp' or check the controller's ARP configuration via 'show running-config | include arp'. Verify that ARP handling is active for wireless clients.
    Affected if ARP processing is enabled and the WLC is handling ARP requests for wireless clients
  4. Check for Layer-3 roaming configuration
    Run 'show mobility' or 'show wireless mobility' on the WLC to check if inter-subnet (Layer-3) roaming is configured. Also verify client roaming settings with 'show client roaming' or similar commands.
    Affected if Layer-3 (inter-subnet) roaming is enabled between multiple wireless controllers or VLANs
  5. Monitor for ARP storm indicators
    Use SNMP or the WLC CLI to monitor ARP packet rates. Check 'show arp statistics' or interface packet counters for unusually high ARP traffic. Look for spikes in unicast ARP requests.
    Affected if Abnormally high ARP traffic or ARP packet flooding is observed on wireless interfaces or controller uplinks

A user is affected if they are running Cisco WLC software version 3.2, 3.2.116.21, 4.0, 4.0.155.0, or 4.1 with ARP processing and Layer-3 roaming enabled, and are experiencing or vulnerable to ARP storm amplification attacks.

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

Upgrade Cisco WLC software to version 3.2 (post-20070727), 4.0 (post-20070727), or 4.1.180.0 or later to patch this vulnerability.

Fix this in Wireless Lan Controller Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-4011 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2007-4011 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