CVE-2014-3308
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 on Trident line cards in ASR 9000 devices lacks a static punt policer, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted packets, aka Bug ID CSCun83985.
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 confidenceThis is a denial of service vulnerability in Cisco IOS XR running on Trident line cards in ASR 9000 devices. The issue is the absence of a static punt policer, which normally limits the rate of packets forwarded to the CPU for processing. Without this control, remote attackers can send crafted packets to exhaust CPU resources, causing device malfunction.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:P/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.
-
Confirm device is ASR 9000 seriesRun 'show platform' or 'show version' to identify the router model (ASR 9001, 9006, 9010, 9904, 9912, 9922, or ASR 9000 with RSP440)Affected if Device model matches any listed in affected products
-
Confirm IOS XR is runningRun 'show version' and verify the operating system is Cisco IOS XRAffected if Device runs Cisco IOS XR
-
Check for Trident line cardsRun 'show platform' or 'show hw-module' to identify installed line cards and their typeAffected if Device contains Trident-based line cards (verify via 'show diag' or 'show inventory')
-
Verify punt policer configurationRun 'show controller punt-policer' or 'show run | include punt' to check if a static punt policer is configured to limit CPU-bound traffic ratesAffected if No punt policer is configured or the command returns no policer entries (device lacks rate limiting on packets forwarded to CPU)
-
Monitor CPU utilization under traffic loadRun 'show processes cpu' or 'show platform cpu' during normal and peak traffic to observe CPU usage patternsAffected if CPU utilization spikes excessively or shows sustained high usage when receiving traffic, indicating possible punt police exhaustion
Device is affected if it is an ASR 9000 series router running IOS XR with Trident line cards and lacks a configured static punt policer to limit punt traffic rates.
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 dataApply the Cisco IOS XR software update that includes the punt policer fix (contact Cisco for specific fixed versions). Until patched, implement network-level access controls to limit exposure to untrusted sources reaching affected line cards.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3308 — 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-3308 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