Ios XeOperating system · Cisco
CVE-2016-1344
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 IKEv2 implementation in Cisco IOS 15.0 through 15.6 and IOS XE 3.3 through 3.17 allows remote attackers to cause a denial of service (device reload) via fragmented packets, aka Bug ID CSCux38417.
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 confidenceA denial of service vulnerability exists in Cisco IOS 15.0-15.6 and IOS XE 3.3-3.17 IKEv2 implementations. Remote attackers can send specially crafted fragmented packets to trigger a device reload, causing service interruption.
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.3s_3.3.0s= 3.3s_3.3.1s= 3.3s_3.3.2s= 3.3sg_3.3.0sg= 3.3sg_3.3.1sg= 3.3sg_3.3.2sg= 3.3xo_3.3.0xo= 3.3xo_3.3.1xo= 3.3xo_3.3.2xo= 3.4s_3.4.0as= 3.4s_3.4.0s= 3.4s_3.4.1s< m16kt61a< 2017-01-06= t-ms14jakucb-1102.5= snv_124< 2.50\(aazi.0\)c0= 3.08CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Determine Cisco IOS/IOS XE versionRun 'show version' on the device CLI and locate the version string (e.g., 15.2(4)E or 3.10.XE)Affected if Version is 15.0 through 15.6 for IOS, or 3.3 through 3.17 for IOS XE (or matches one of the specific affected builds like 3.3s_3.3.0s, 3.3sg_3.3.0sg, etc.)
-
Confirm IKEv2 is configuredRun 'show crypto ikev2 session' or 'show running-config | include ikev2' to check for active IKEv2 configurationsAffected if IKEv2 is enabled or configured on any interface reachable from untrusted networks
-
Verify IKEv2 interface exposureReview interface configurations with 'show ip interface' and check if IKEv2 peers are reachable from external/untrusted networksAffected if Any IKEv2-configured interface is directly accessible from untrusted networks such as the internet
-
Check non-Cisco firmware versions (if applicable)For listed products (Lenovo Thinkcentre E75s, Netgear Jr6150, Samsung X14j, Zyxel GS1900), use vendor-specific commands or web UI to retrieve firmware versionAffected if Firmware version is below vendor-specific threshold: Lenovo < m16kt61a, Netgear < 2017-01-06, Zyxel < 2.50(aazi.0)c0, or matches specific versions listed (Samsung = t-ms14jakucb-1102.5, Sun Opensolaris = snv_124, Zzinc = 3.08)
The environment is affected if the device runs a Cisco IOS version 15.0-15.6 or IOS XE 3.3-3.17 (or matching the specific build identifiers), OR runs any of the non-Cisco firmware versions listed, AND has IKEv2 enabled with network exposure to untrusted sources.
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 data2.502017-01-06
Upgrade to a patched Cisco IOS/IOS XE version beyond 15.6/3.17. If immediate patching is not feasible, consider filtering IKEv2 traffic from untrusted sources at network perimeter devices.
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-2016-1344 — 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-2016-1344 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