iOSOperating system · Cisco
CVE-2014-2107
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 12.2 and 15.0 through 15.3, when used with the Kailash FPGA before 2.6 on RSP720-3C-10GE and RSP720-3CXL-10GE devices, allows remote attackers to cause a denial of service (route switch processor outage) via crafted IP packets, aka Bug ID CSCug84789.
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 confidenceDenial of service vulnerability in Cisco IOS 12.2 and 15.0-15.3 when running on RSP720-3C-10GE and RSP720-3CXL-10GE router switch processors with Kailash FPGA firmware before version 2.6. Remote attackers can send crafted IP packets to trigger a route switch processor outage.
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
= 12.2= 15.0= 15.0\(1\)se= 15.1= 15.2= 15.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router switch processor modelExecute 'show module' or 'show hardware' command on the Cisco device to confirm the model is RSP720-3C-10GE or RSP720-3CXL-10GEAffected if The hardware is NOT an RSP720-3C-10GE or RSP720-3CXL-10GE (different models are not affected by this specific CVE)
-
Determine the Cisco IOS versionExecute 'show version' to display the installed IOS version; check if it matches 12.2, 15.0, 15.0(1)se, 15.1, 15.2, or 15.3Affected if The IOS version falls within 12.2 or 15.0-15.3 range (these are the affected versions per the CVE)
-
Locate the Kailash FPGA firmware versionExecute 'show hardware' or 'show firmware' command; look for Kailash FPGA firmware version information on the RSP moduleAffected if The Kailash FPGA firmware version is below 2.6 (versions prior to 2.6 are vulnerable)
-
Confirm IP packet processing is enabledVerify the router is configured to process IP traffic on the RSP720 modules; check interface status with 'show ip interface brief' to confirm IP is enabled on active interfacesAffected if IP is enabled and the device is actively processing IP packets (the attack vector requires crafted IP packets to reach the device)
You are affected if your device uses an RSP720-3C-10GE or RSP720-3CXL-10GE processor, runs IOS 12.2 or 15.0-15.3, and has Kailash FPGA firmware earlier than version 2.6.
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 dataUpdate Kailash FPGA firmware to version 2.6 or later on affected RSP modules; ensure IOS is updated to a compatible version. Consider network segmentation or ACLs to limit exposure until patching is possible.
Fix this in iOS
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-2107 — 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-2107 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