Ios XeOperating system · Cisco
CVE-2014-2183
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 · uneditedThe L2TP module in Cisco IOS XE 3.10S(.2) and earlier on ASR 1000 routers allows remote authenticated users to cause a denial of service (ESP card reload) via a malformed L2TP packet, aka Bug ID CSCun09973.
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 confidenceThe L2TP module in Cisco IOS XE 3.10S(.2) and earlier on ASR 1000 routers contains a vulnerability where processing a malformed L2TP packet by an authenticated remote user triggers an ESP (Encapsulating Security Payload) card reload, causing denial of service.
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 XeOperating system
<= 3.10.2s= 3.10= 3.10.0s= 3.10.1s= 3.10.1s1
Asr 1001Hardware / appliance
all versions
Asr 1002Hardware / appliance
all versions
Asr 1002 XHardware / appliance
all versions
Asr 1002 Fixed RouterHardware / appliance
all versions
Asr 1004Hardware / appliance
all versions
Asr 1006Hardware / appliance
all versions
Asr 1013Hardware / 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
- M
- Authentication
- Single
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:M/Au:S/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 hardware modelRun 'show version' or 'show platform' to confirm the device is an ASR 1000 series router (ASR 1001, 1002, 1002X, 1004, 1006, or 1013)Affected if Device is any ASR 1000 series model listed in affected products
-
Check IOS XE versionRun 'show version' and locate the Cisco IOS XE software version stringAffected if Version matches 3.10, 3.10.0S, 3.10.1S, 3.10.1S1, 3.10.2S, or any version <=3.10.2S on the ASR 1000 platform
-
Verify L2TP is configuredRun 'show running-config | include l2tp' or 'show running-config | section l2tp' to check for L2TP-related configurationAffected if L2TP configuration exists (such as vpdn-group, l2tp enable, or l2tp tunnel settings)
-
Confirm L2TP feature is enabledRun 'show feature | include l2tp' to check if the L2TP feature set is enabledAffected if L2TP feature is active or enabled on the device
-
Check for active L2TP sessions or tunnelsRun 'show l2tp session' or 'show l2tp tunnel' to see if L2TP sessions are activeAffected if Any L2TP tunnels or sessions are established, indicating the device is processing L2TP traffic
The environment is affected if the device is an ASR 1000 series running IOS XE 3.10.x and has L2TP configured or enabled, as the vulnerability triggers when processing malformed L2TP packets.
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 XE software update that addresses CSCun09973. If a patch is unavailable, consider filtering L2TP traffic at network boundaries or implementing access controls to limit which authenticated users can initiate L2TP sessions.
Fix this in Ios Xe
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-2183 — 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-2183 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