dbcve.org
iOSOperating system · Cisco

CVE-2014-3354

HIGH · 7.8 CVSS v2.0 Published 2014-09-25
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
Cisco IOS 12.0, 12.2, 12.4, 15.0, 15.1, 15.2, and 15.3 and IOS XE 2.x and 3.x before 3.7.4S; 3.2.xSE and 3.3.xSE before 3.3.2SE; 3.3.xSG and 3.4.xSG before 3.4.4SG; and 3.8.xS, 3.9.xS, and 3.10.xS before 3.10.1S allow remote attackers to cause a denial of service (device reload) via malformed RSVP packets, aka Bug ID CSCui11547.

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

The vulnerability allows remote attackers to cause Cisco IOS and IOS XE devices to reload (denial of service) by sending malformed RSVP (Resource Reservation Protocol) packets. This affects multiple IOS and IOS XE version families across versions 12.0 through 15.3 and several XE branches.

MitigationApply the appropriate Cisco IOS/IOS XE software updates as specified in the Cisco advisory. If patching is not immediately feasible, consider filtering or rate-limiting RSVP traffic at network borders to reduce attack surface.

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.0= 12.2= 12.4= 15.0= 15.1= 15.2= 15.3
Ios XeOperating system
Affected:= 2.1= 2.1.0= 2.1.1= 2.1.2= 2.2= 2.2.1= 2.2.2= 2.2.3= 2.3= 2.3.0= 2.3.1= 2.3.1t

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 device OS and version
    Run the command 'show version' on the Cisco device to obtain the iOS or IOS XE version number
    Affected if The device runs Cisco IOS or IOS XE and the version falls within the affected ranges (12.0, 12.2, 12.4, 15.0, 15.1, 15.2, 15.3 for iOS, or 2.1.x through 2.3.1t for IOS XE)
  2. Verify RSVP is enabled on the device
    Run 'show ip rsvp' or check the configuration with 'show running-config | include rsvp' to determine if RSVP is configured
    Affected if RSVP is enabled or configured on the device - the vulnerability only affects devices where RSVP is actively running
  3. Check which interfaces have RSVP enabled
    Run 'show ip rsvp interface' to list all interfaces with RSVP protocol enabled
    Affected if RSVP is enabled on any interface, exposing that interface to malformed RSVP packet attacks

A device is affected only if it runs a vulnerable Cisco IOS or IOS XE version AND has RSVP enabled on the system or at least one 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 appropriate Cisco IOS/IOS XE software updates as specified in the Cisco advisory. If patching is not immediately feasible, consider filtering or rate-limiting RSVP traffic at network borders to reduce attack surface.

Fix this in iOS Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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