Wireless Lan Controller SoftwareOperating system · Cisco

CVE-2013-1103

HIGH · 7.8 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 →

87/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Cisco Wireless LAN Controller (WLC) devices with software 7.0 before 7.0.220.0, 7.1 before 7.1.91.0, and 7.2 before 7.2.103.0 allow remote attackers to cause a denial of service (Access Point reload) via crafted SIP packets, aka Bug ID CSCts87659.

Technical summary

dbcve analysis · high confidence

This is a denial of service vulnerability in Cisco Wireless LAN Controller (WLC) devices. Attackers can send specially crafted SIP (Session Initiation Protocol) packets to affected devices, causing associated Access Points to reload and disconnect wireless clients. The vulnerability affects WLC software versions 7.0 before 7.0.220.0, 7.1 before 7.1.91.0, and 7.2 before 7.2.103.0.

MitigationUpgrade Cisco WLC software to version 7.0.220.0, 7.1.91.0, 7.2.103.0 or later. As a temporary measure, consider blocking or rate-limiting SIP traffic at network boundaries if the upgrade cannot be immediately applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Wireless Lan Controller SoftwareOperating system

Affected:= 7.0= 7.0.98.0= 7.1= 7.2= 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

4100 Wireless Lan ControllerHardware / appliance

Affected:all versions

4400 Wireless Lan ControllerHardware / appliance

Affected:all versions

5500 Wireless Lan ControllerHardware / appliance

Affected:all versions

7500 Wireless Lan ControllerHardware / appliance

Affected:all versions

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: None
Integrity: None
Availability: Complete

AV:N/AC:L/Au:N/C:N/I:N/A:C

Am I affected?

dbcve checks

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

Identify the Cisco WLC model

Log into the WLC CLI or web interface and run 'show inventory' or check the device model in the web interface under Monitor > Controller > Summary

Affected if The device is one of these models: Cisco 2000, 2100, 2500, 4100, 4400, 5500, or 7500 Wireless LAN Controller
Check the WLC software version

Run 'show sysinfo' or 'show version' from the CLI, or check in the web interface under Monitor > Controller > Summary

Affected if The running software version is 7.0.x before 7.0.220.0, 7.1.x before 7.1.91.0, or 7.2.x before 7.2.103.0
Verify if SIP is enabled on the WLC

Run 'show sip' from the CLI, or check in the web interface under Wireless > SIP > SIP Security. Also check 'show run-config' for any sip-related configuration

Affected if SIP functionality is enabled or configured on the controller
Check for SIP traffic processing

Monitor network traffic or check WLC logs for SIP packets. Run 'show client summary' to see if SIP-based phones or devices are connected

Affected if SIP traffic is being processed or SIP-based devices are associated to the wireless network

A user is affected if they are running a Cisco WLC with a vulnerable software version (7.0 before 7.0.220.0, 7.1 before 7.1.91.0, or 7.2 before 7.2.103.0) and have SIP enabled or SIP devices connected.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade Cisco WLC software to version 7.0.220.0, 7.1.91.0, 7.2.103.0 or later. As a temporary measure, consider blocking or rate-limiting SIP traffic at network boundaries if the upgrade cannot be immediately applied.

Fix this in Wireless Lan Controller Software Scoped from the published advisory

Consultation4.0 h
Implementation3.0 h
Testing4.0 h
Review / QA2.0 h

13.0 hours of engineering $2,300

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-1103 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2013-1103?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 1.8%

Affects: Wireless Lan Controller Software

Remediation

A high-priority fix

Fix this in Wireless Lan Controller Software 13 hrs · Moderate

Typical engagement from $2,300

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2013-1103 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References