Ios XeOperating system · Cisco
CVE-2015-0641
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.9.0S, 3.10 before 3.10.0S, 3.11 before 3.11.0S, 3.12 before 3.12.0S, 3.13 before 3.13.0S, 3.14 before 3.14.0S, and 3.15 before 3.15.0S allows remote attackers to cause a denial of service (device reload) via crafted IPv6 packets, aka Bug ID CSCub68073.
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 XE where specially crafted IPv6 packets can cause the device to reload unexpectedly. The vulnerability affects multiple version branches (2.x, 3.x) prior to specific patch release thresholds (3.9.0S, 3.10.0S, 3.11.0S, 3.12.0S, 3.13.0S, 3.14.0S, and 3.15.0S). Remote attackers can trigger this condition without authentication, leading to service disruption.
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.1s.0= 3.1s.1= 3.1s.2= 3.1s.3= 3.1s.4= 3.1s.5= 3.1s.6= 3.2s.0= 3.2s.1= 3.2s.2= 3.2s.3= 3.3s.0CVSS 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.
-
Check the IOS XE versionRun 'show version' on the device and locate the version string (typically in the format 3.Xs.Y)Affected if The version is 3.1s.0 through 3.3s.0 (including 3.1s.1, 3.1s.2, 3.1s.3, 3.1s.4, 3.1s.5, 3.1s.6, 3.2s.0, 3.2s.1, 3.2s.2, 3.2s.3, 3.3s.0)
-
Verify if IPv6 is enabledRun 'show ipv6 interface brief' to list interfaces with IPv6 enabled, or check the running configuration for 'ipv6 enable' under interface settingsAffected if IPv6 is enabled on any device interface - the vulnerability is triggered by specially crafted IPv6 packets
-
Confirm IPv6 network exposureCheck if the device has IPv6 addresses on interfaces facing untrusted networks (WAN, DMZ, or internet-connected interfaces). Use 'show ipv6 interface' to view IPv6 addresses and their scopeAffected if The device is reachable via IPv6 from untrusted networks - remote attackers need to send packets to the device
-
Check the installed release trainRun 'show version' and identify the release train (the S suffix indicates maintenance releases). Compare against the patched thresholds: 3.9.0S, 3.10.0S, 3.11.0S, 3.12.0S, 3.13.0S, 3.14.0S, or 3.15.0SAffected if The installed version is below the patched threshold for your specific release branch
The device is affected if it runs Cisco IOS XE version 3.1s.0 through 3.3s.0, has IPv6 enabled, and is reachable via IPv6 from untrusted networks.
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 dataUpgrade Cisco IOS XE to a version at or above the patched release thresholds (3.9.0S, 3.10.0S, 3.11.0S, 3.12.0S, 3.13.0S, 3.14.0S, or 3.15.0S depending on the installed branch). If immediate upgrade is not feasible, consider IPv6 access control lists to filter untrusted IPv6 traffic.
Fix this in Ios Xe
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0641 — 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-2015-0641 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