Ios XrOperating system · Cisco
CVE-2014-3376
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 · uneditedCisco IOS XR 5.1 and earlier allows remote attackers to cause a denial of service (process reload) via a malformed RSVP packet, aka Bug ID CSCuq12031.
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 confidenceA vulnerability in Cisco IOS XR 5.1 and earlier allows remote unauthenticated attackers to send malformed RSVP (Resource Reservation Protocol) packets that cause a process reload, resulting in denial of service. The attack requires only network access to the affected device's RSVP-facing interface.
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
= 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.1CVSS 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
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if device runs Cisco IOS XRExecute 'show version' on the device and examine the output for 'IOS XR' in the software identification lineAffected if The output does not show 'IOS XR' - the device is not affected by this specific IOS XR vulnerability
-
Determine the IOS XR versionExecute 'show version' and locate the version number in the output (e.g., 'Version 4.3.0')Affected if The installed version is 5.1 or earlier, or matches any of these: 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 - the device falls within the affected version range
-
Verify if RSVP protocol is enabledExecute 'show rsvp interface' or 'show rsvp' to list interfaces with RSVP enabledAffected if No output or RSVP not listed - RSVP is not enabled, making the device not vulnerable to this specific attack vector
-
Assess network exposure of RSVP-facing interfacesReview interface configurations and network topology to determine if the RSVP-enabled interface is reachable from untrusted networksAffected if The RSVP interface is directly accessible from external/untrusted networks - combined with affected version and RSVP enabled, the device is vulnerable to remote unauthenticated attack
A device is affected if it runs Cisco IOS XR version 5.1 or earlier, has RSVP protocol enabled on a network-accessible interface, and the RSVP-facing interface is reachable from untrusted networks.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Cisco IOS XR to a version later than 5.1 that contains the fix for CSCuq12031. If immediate patching is not feasible, consider filtering or rate-limiting RSVP traffic at network boundaries to reduce exposure.
Fix this in Ios Xr
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2014-3376 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-3376 in production — separate from our analysis above.
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.
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.
- 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