Ios XeOperating system · Cisco
CVE-2015-6269
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 before 2.2.3 on ASR 1000 devices allows remote attackers to cause a denial of service (Embedded Services Processor crash) via a crafted (1) IPv4 or (2) IPv6 packet, aka Bug ID CSCsw69990.
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 confidenceDenial of service vulnerability in Cisco IOS XE before version 2.2.3 on ASR 1000 routers where specially crafted IPv4 or IPv6 packets cause the Embedded Services Processor (ESP) to crash, resulting in loss of packet forwarding capabilities.
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
= 2.2.1= 2.2.2CVSS 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.
-
Confirm device is ASR 1000 seriesRun 'show version' or 'show hardware' and verify the model number indicates ASR 1000 (e.g., ASR-1001-X, ASR-1002-X, ASR-1004, ASR-1006)Affected if Device is not a Cisco ASR 1000 series router - the vulnerability does not apply to other platforms
-
Check IOS XE versionRun 'show version' and locate the 'IOS XE' or 'Version' line. The version will be displayed as something like 2.2.1 or 2.2.2Affected if Version is exactly 2.2.1 or 2.2.2 - these are the only affected versions listed
-
Verify IPv4 or IPv6 forwarding is enabledRun 'show ip forwarding' for IPv4 and 'show ipv6 forwarding' for IPv6. Both are typically enabled by default on ASR 1000 devicesAffected if IPv4 or IPv6 forwarding is enabled - the crafted packets must be able to reach the ESP for the crash to occur
-
Check ESP processor statusRun 'show platform' or 'show esp status' to verify the Embedded Services Processor is present and operationalAffected if ESP processor is present and active - this is the component that crashes when specially crafted packets are received
The device is affected if it is a Cisco ASR 1000 series router running IOS XE version 2.2.1 or 2.2.2 with IPv4/IPv6 forwarding enabled and an ESP processor present.
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 on affected ASR 1000 devices to version 2.2.3 or later; apply latest available patch from Cisco and schedule appropriate maintenance window given CVSS 7.8 severity.
Fix this in Ios Xe
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6269 — 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-6269 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