Ios XrOperating system · Cisco
CVE-2014-3396
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 ASR 9000 devices does not properly use compression for port-range and address-range encoding, which allows remote attackers to bypass intended Typhoon line-card ACL restrictions via transit traffic, aka Bug ID CSCup30133.
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 · moderate confidenceCisco IOS XR on ASR 9000 devices contains a flaw in how the Typhoon line-card processes ACLs with port-range and address-range encoding. The compression mechanism used for these ranges is improper, allowing transit traffic to bypass configured ACL restrictions. An unauthenticated remote attacker can send specially crafted packets that circumvent intended access controls.
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
all versions
Asr 9000 Rsp440 RouterHardware / appliance
all versions
Asr 9001Hardware / appliance
all versions
Asr 9006Hardware / appliance
all versions
Asr 9010Hardware / appliance
all versions
Asr 9904Hardware / appliance
all versions
Asr 9912Hardware / appliance
all versions
Asr 9922Hardware / appliance
all 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/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.
-
Identify device model and confirm it is an ASR 9000 seriesRun 'show platform' or 'show version' to confirm the hardware is an ASR 9000, ASR 9001, ASR 9006, ASR 9010, ASR 9904, ASR 9912, or ASR 9922Affected if Device is not one of the listed ASR 9000 series models, then not affected by this specific CVE
-
Verify Cisco IOS XR is the running OSRun 'show version' and confirm the OS is Cisco IOS XRAffected if Device does not run IOS XR, then not affected by this CVE
-
Identify Typhoon line-cards in useRun 'show platform' or 'show controller fabric' to identify if Typhoon line-cards are installedAffected if No Typhoon line-cards present, then not affected (vulnerability is specific to Typhoon line-card ACL processing)
-
Check for ACLs with port-range or address-range configurationsRun 'show access-lists' and review ACL entries for 'range' keywords in port or address specificationsAffected if No ACLs configured with port-range or address-range encoding, then not vulnerable to this specific bypass vector
The device is affected only if it is an ASR 9000 series running IOS XR with Typhoon line-cards and has ACLs configured using port-range or address-range encoding.
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 for Bug ID CSCup30133 when available. In the interim, implement compensating controls such as additional filtering at upstream devices or alternative ACL implementations that avoid the vulnerable encoding patterns.
Fix this in Ios Xr
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3396 — 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-3396 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