dbcve.org
Ios XeOperating system · Cisco

CVE-2015-6270

HIGH · 7.8 CVSS v2.0 Published 2015-08-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Cisco IOS XE before 2.2.3 on ASR 1000 devices allows remote attackers to cause a denial of service (Embedded Services Processor crash) via a crafted IPv6 packet, aka Bug ID CSCsv98555.

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 confidence

A denial-of-service vulnerability in Cisco IOS XE before version 2.2.3 on ASR 1000 devices allows remote attackers to crash the Embedded Services Processor (ESP) by sending a specially crafted IPv6 packet. The vulnerability is in the IPv6 packet processing path and can be exploited without authentication.

MitigationUpgrade Cisco IOS XE to version 2.2.3 or later on affected ASR 1000 devices. If immediate patching is not possible, consider filtering or rate-limiting unexpected IPv6 traffic at network perimeter as a temporary mitigation until the update can be applied.

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
Affected:= 2.2.1= 2.2.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Run 'show version' or 'show platform' command and look for ASR 1000 series in the output
    Affected if Device is not a Cisco ASR 1000 series router - this CVE only affects ASR 1000 platforms
  2. Check the IOS XE version
    Run 'show version' and locate the 'IOS XE' version number in the output. Compare it to the affected versions 2.2.1 and 2.2.2
    Affected if IOS XE version is exactly 2.2.1 or 2.2.2 - only these versions are vulnerable
  3. Verify IPv6 is enabled
    Run 'show ipv6 interface brief' to check if any IPv6 interfaces are configured and active
    Affected if IPv6 is enabled on any interface - the vulnerability lies in the IPv6 packet processing path, so IPv6 must be active for exploitation
  4. Check ESP status after receiving IPv6 traffic
    Monitor output of 'show platform' or 'show esp hardware' command, particularly after the device processes IPv6 traffic
    Affected if ESP shows crash, reload, or abnormal status - the vulnerability causes ESP crashes when specially crafted IPv6 packets are processed

Device is affected if it is a Cisco ASR 1000 running IOS XE version 2.2.1 or 2.2.2 with IPv6 enabled and exposed to untrusted IPv6 traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco IOS XE to version 2.2.3 or later on affected ASR 1000 devices. If immediate patching is not possible, consider filtering or rate-limiting unexpected IPv6 traffic at network perimeter as a temporary mitigation until the update can be applied.

Fix this in Ios Xe Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6270 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-6270 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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