dbcve.org
Ios XrOperating system · Cisco

CVE-2014-3379

MEDIUM · 6.1 CVSS v2.0 Published 2014-09-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
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 5.1 and earlier on Network Convergence System 6000 devices allows remote attackers to cause a denial of service (NPU and card hang or reload) via a malformed MPLS packet, aka Bug ID CSCuq10466.

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 in Cisco IOS XR 5.1 and earlier on Network Convergence System 6000 (NCS 6000) devices allows remote attackers to send malformed MPLS packets that cause the NPU (Network Processing Unit) and line cards to hang or force a reload. The vulnerability stems from insufficient validation of MPLS packet headers upon processing.

MitigationUpgrade Cisco IOS XR to a version later than 5.1 that includes the fix for Bug ID CSCuq10466. If immediate patching is not possible, consider implementing ACLs or traffic filtering at network edges to drop malformed MPLS packets before they reach affected devices.

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:= 2.0= 3.0= 3.0.1= 3.1= 3.1.0= 3.2= 3.2.1= 3.2.2= 3.2.4= 3.2.50= 3.3= 3.3.1
Network Convergence System 6000Hardware / appliance
Affected:all versions
Network Convergence System 6008Hardware / 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
Adjacent
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:A/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 device model
    Run 'show platform' or check hardware inventory to confirm the device is a Cisco Network Convergence System 6000 (NCS 6000) or NCS 6008, or run 'show version' to identify the IOS XR software
    Affected if Device model is NCS 6000 or NCS 6008, or software is Cisco IOS XR
  2. Check IOS XR version
    Run 'show version' command to display the installed Cisco IOS XR version
    Affected if Version is 2.0, 3.0, 3.0.1, 3.1, 3.1.0, 3.2, 3.2.1, 3.2.2, 3.2.4, 3.2.50, 3.3, or 3.3.1, or for NCS 6000/6008 any version (all versions affected)
  3. Verify MPLS is enabled
    Run 'show mpls interfaces' or 'show running-config mpls' to check if MPLS is configured on any interface
    Affected if MPLS is enabled and processing traffic on any interface

You are affected if you run Cisco IOS XR versions 2.0 through 3.3.1, or any NCS 6000/6008 version, with MPLS enabled and processing traffic.

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 IOS XR to a version later than 5.1 that includes the fix for Bug ID CSCuq10466. If immediate patching is not possible, consider implementing ACLs or traffic filtering at network edges to drop malformed MPLS packets before they reach affected devices.

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-3379 — 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-2014-3379 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