dbcve.org
Wireless Lan Controller SoftwareOperating system · Cisco

CVE-2013-1105

HIGH · 9.0 CVSS v2.0 Published 2013-01-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable 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 Wireless LAN Controller (WLC) devices with software 7.0 before 7.0.235.3, 7.1 and 7.2 before 7.2.111.3, and 7.3 before 7.3.101.0 allow remote authenticated users to bypass wireless-management settings and read or modify the device configuration via an SNMP request, aka Bug ID CSCua60653.

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

Cisco Wireless LAN Controller devices running software versions 7.0 before 7.0.235.3, 7.1 and 7.2 before 7.2.111.3, and 7.3 before 7.3.101.0 contain a vulnerability where remote authenticated users can bypass wireless-management settings via SNMP requests, allowing unauthorized read or modification of device configuration.

MitigationApply the vendor-supplied software updates to reach version 7.0.235.3, 7.2.111.3, or 7.3.101.0 or later. Additionally, restrict SNMP access to trusted management networks and use SNMPv3 with authentication/encryption.

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:= 7.0= 7.0.98.0= 7.0.220.0= 7.1= 7.2= 7.2.103.0= 7.2.110.0= 7.3
2000 Wireless Lan ControllerHardware / appliance
Affected:all versions
2100 Wireless Lan ControllerHardware / appliance
Affected:all versions
2500 Wireless Lan ControllerHardware / appliance
Affected:all versions
5500 Wireless Lan ControllerHardware / appliance
Affected:all versions
7500 Wireless Lan ControllerHardware / appliance
Affected:all versions
8500 Wireless Lan ControllerHardware / appliance
Affected:all versions

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

AV:N/AC:L/Au:S/C:C/I:C/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 the WLC hardware model
    Run 'show inventory' or check the device chassis label to determine if the model is a Cisco 2000, 2100, 2500, 5500, 7500, or 8500 Wireless LAN Controller
    Affected if The model is any of these hardware platforms (all versions are affected)
  2. Determine the software version
    Run 'show version' on the WLC CLI to retrieve the installed software version number
    Affected if The version is 7.0 before 7.0.235.3, 7.1, 7.2 before 7.2.111.3, or 7.3 before 7.3.101.0
  3. Verify SNMP is configured
    Run 'show snmp' or 'show snmp community' to check if SNMP is enabled and which communities are configured
    Affected if SNMP is enabled and accessible to the attacker (the vulnerability is exploited via SNMP requests)
  4. Confirm SNMP access scope
    Check the SNMP access control configuration via 'show snmp' or review the management interface ACLs to determine if SNMP is exposed to untrusted networks
    Affected if SNMP is accessible from non-management or untrusted networks

The environment is affected if the WLC is a 2000/2100/2500/5500/7500/8500 model (any version) OR runs software 7.0 before 7.0.235.3, 7.1, 7.2 before 7.2.111.3, or 7.3 before 7.3.101.0, and SNMP is enabled and accessible to the attacker.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied software updates to reach version 7.0.235.3, 7.2.111.3, or 7.3.101.0 or later. Additionally, restrict SNMP access to trusted management networks and use SNMPv3 with authentication/encryption.

Recommended fix High confidence

Upgrade to 7.0.235.3 (or later 7.0.x), 7.2.111.3 (or later 7.2.x), or 7.3.101.0 (or later 7.3.x) depending on your current branch

  1. 1. Identify the current WLC model and software version by running 'show version' on the device
  2. 2. Determine the appropriate fixed version based on current software branch: for 7.0.x use 7.0.235.3 or later, for 7.1/7.2.x use 7.2.111.3 or later, for 7.3.x use 7.3.101.0 or later
  3. 3. Download the fixed software image from Cisco.com (requires valid Cisco service contract)
  4. 4. Backup the current device configuration using the WLC web interface or CLI 'save config' command
  5. 5. Upload the new firmware to the WLC via TFTP, FTP, or the web interface
  6. 6. Reboot the controller to apply the new software version
  7. 7. After reboot, verify the new version is running with 'show version'
  8. 8. Restrict SNMP access by using ACLs or disabling SNMP write access if not required
Caveat Ensure the new version supports your specific WLC model; some legacy models may have limited upgrade paths; test configuration compatibility in a lab environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

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
14.0 hours of engineering $2,480
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1105 — 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-2013-1105 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