Ios XrOperating system · Cisco

CVE-2014-2176

HIGH · 7.1 CVSS v2.0 Published 2014-06-14
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 IOS XR 4.1.2 through 5.1.1 on ASR 9000 devices, when a Trident-based line card is used, allows remote attackers to cause a denial of service (NP chip and line card reload) via malformed IPv6 packets, aka Bug ID CSCun71928.

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 IOS XR versions 4.1.2 through 5.1.1 on ASR 9000 routers with Trident-based line cards contain a vulnerability where processing malformed IPv6 packets causes the Network Processor (NP) chip and line card to reload, resulting in denial of service. The attack is remote and requires no authentication.

MitigationApply the Cisco fix for Bug ID CSCun71928 (IOS XR software update). If immediate patching is not possible, consider IPv6 traffic filtering or segmentation to reduce attack surface until the update can be deployed.

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
Ios XrOperating system
Affected:= 4.1.2= 4.2.0= 4.3.1= 5.1.0= 5.1.1
Asr 9001Hardware / appliance
Affected:all versions
Asr 9006Hardware / appliance
Affected:all versions
Asr 9010Hardware / appliance
Affected:all versions
Asr 9904Hardware / appliance
Affected:all versions
Asr 9912Hardware / appliance
Affected:all versions
Asr 9922Hardware / 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
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 the router model
    Run 'show version' or 'show platform' and confirm the device is an ASR 9001, ASR 9006, ASR 9010, ASR 9904, ASR 9912, or ASR 9922
    Affected if The device is any of these ASR 9000 series models
  2. Check the IOS XR version
    Run 'show version' and locate the IOS XR software version string
    Affected if The version is 4.1.2, 4.2.0, 4.3.1, 5.1.0, or 5.1.1 (or any version in the range 4.1.2 through 5.1.1)
  3. Verify Trident-based line cards are present
    Run 'show platform' or 'show hardware' and look for Trident line card modules in the chassis
    Affected if Trident-based Network Processor line cards are installed and active
  4. Check if IPv6 is enabled
    Run 'show ipv6 interface brief' to list interfaces with IPv6 configured and active
    Affected if IPv6 is enabled on any interface - the vulnerability triggers when malformed IPv6 packets are processed

The environment is affected if it is an ASR 9000 series router running IOS XR version 4.1.2 through 5.1.1 with Trident-based line cards and IPv6 is enabled on any interface.

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 Cisco fix for Bug ID CSCun71928 (IOS XR software update). If immediate patching is not possible, consider IPv6 traffic filtering or segmentation to reduce attack surface until the update can be deployed.

Fix this in Ios Xr Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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