Ios XeOperating system · Cisco
CVE-2013-1165
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 XE 2.x and 3.x before 3.4.5S, and 3.5 through 3.7 before 3.7.1S, on 1000 series Aggregation Services Routers (ASR) allows remote attackers to cause a denial of service (card reload) by sending many crafted L2TP packets, aka Bug ID CSCtz23293.
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 confidenceCisco IOS XE on ASR 1000 series routers contains a vulnerability in L2TP packet processing that allows remote attackers to cause denial of service via card reload by sending crafted L2TP packets. The vulnerability affects versions 2.x and 3.x before 3.4.5S, and 3.5-3.7 before 3.7.1S.
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.4.3s= 2.1.0= 2.1.1= 2.1.2= 2.2.1= 2.2.2= 2.2.3= 2.3.0= 2.3.1= 2.3.1t= 2.3.2= 2.4.0
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 1023 RouterHardware / 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelExecute 'show version' or 'show platform' to confirm the hardware is an ASR 1000 series router (ASR 1001, 1002, 1002-X, 1004, 1006, or 1023)Affected if Device is any ASR 1000 series model listed in the affected products
-
Determine the IOS XE versionExecute 'show version' and locate the IOS XE version string (for example, 2.1.0, 2.4.0, 3.4.3S, 3.7.0S)Affected if Version is 2.x, 3.x before 3.4.5S, or 3.5-3.7 before 3.7.1S (including all specific versions listed in the advisory)
-
Verify L2TP is enabledExecute 'show running-config | include l2tp' or 'show ip interface' to check for L2TP tunnel configurationAffected if L2TP is actively configured on any interface (the vulnerability requires L2TP packet processing to be active)
Device is affected if it is an ASR 1000 series running an affected IOS XE version (2.x, 3.x before 3.4.5S, or 3.5-3.7 before 3.7.1S) and L2TP feature or tunnels are enabled.
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 appropriate Cisco IOS XE software update (3.4.5S or 3.7.1S or later) after verifying current version and testing in a non-production environment. If immediate patching is not feasible, consider network segmentation to limit exposure to untrusted L2TP traffic sources.
Fix this in Ios Xe
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1165 — 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-2013-1165 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