dbcve.org
iOSOperating system · Cisco

CVE-2011-3282

HIGH · 7.8 CVSS v2.0 Published 2011-10-03
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 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
Unspecified vulnerability in Cisco IOS 12.2SRE before 12.2(33)SRE4, 15.0, and 15.1, and IOS XE 2.1.x through 3.3.x, when an MPLS domain is configured, allows remote attackers to cause a denial of service (device reload) via an ICMPv6 packet, related to an expired MPLS TTL, aka Bug ID CSCtj30155.

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 IOS 12.2SRE, 15.0/15.1 and IOS XE 2.1.x-3.3.x when an MPLS domain is configured. Remote attackers can send specially crafted ICMPv6 packets that trigger an expired MPLS TTL condition, causing the device to reload unexpectedly.

MitigationApply Cisco IOS updates (12.2(33)SRE4 or later for 12.2SRE branch; vendor patches for 15.x and IOS XE). As interim mitigation, consider filtering or rate-limiting ICMPv6 traffic at network borders if MPLS is not required.

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
iOSOperating system
Affected:= 12.2\(33\)sre= 12.2\(33\)sre0a= 12.2\(33\)sre1= 12.2\(33\)sre2= 12.2\(33\)sre3= 12.2sre= 15.0= 15.1
Ios XeOperating system
Affected:= 2.1.0= 2.1.1= 2.1.2= 2.2.1= 2.2.2= 2.2.3= 2.3.0= 2.3.1= 2.3.2= 2.4.0= 2.4.1= 2.4.2

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

AV:N/AC:L/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 the Cisco IOS/IOS XE version
    Use the command 'show version' on the device console or via SSH to retrieve the running software version
    Affected if The version matches any of these: 12.2(33)SRE, 12.2(33)SRE0a, 12.2(33)SRE1, 12.2(33)SRE2, 12.2(33)SRE3, 12.2SRE, 15.0, 15.1 for IOS; or 2.1.0 through 2.4.2 for IOS XE
  2. Verify MPLS is enabled
    Use 'show mpls interface' or 'show running-config | include mpls' to check if MPLS is configured on any interface
    Affected if MPLS is actively configured on one or more interfaces
  3. Confirm IPv6 is operational
    Use 'show ipv6 interface brief' to see if IPv6 is enabled on any interface
    Affected if IPv6 interfaces are up and processing traffic
  4. Check for ICMPv6 traffic handling
    Use 'show ipv6 traffic' or examine ACLs applied to interfaces to verify ICMPv6 packets are permitted
    Affected if ICMPv6 traffic is allowed and processed by the device

The device is affected if it runs an affected IOS/IOS XE version AND has MPLS configured AND has IPv6/ICMPv6 enabled, because the vulnerability requires all three conditions to be present for exploitation.

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 Cisco IOS updates (12.2(33)SRE4 or later for 12.2SRE branch; vendor patches for 15.x and IOS XE). As interim mitigation, consider filtering or rate-limiting ICMPv6 traffic at network borders if MPLS is not required.

Fix this in iOS Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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