CVE-2015-6268
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 IPv4 UDP packet, aka Bug ID CSCsw95482.
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 before version 2.2.3 on ASR 1000 devices contains a vulnerability in IPv4 UDP packet processing that allows remote attackers to crash the Embedded Services Processor (ESP) via crafted UDP packets, causing denial of service.
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= 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 ASR 1000 hardware platformRun 'show version' or 'show inventory' and look for 'ASR' or '1000' in the outputAffected if Device model is not an ASR 1000 series (the vulnerability only affects ASR 1000 devices)
-
Identify IOS XE versionRun 'show version' and locate the 'Cisco IOS XE' version string in the outputAffected if Version is 2.2.1 or 2.2.2 exactly; versions before 2.2.1 are not affected, and 2.2.3 and later contain the fix
-
Check for active IPv4 UDP configurationsRun 'show ip interface' or 'show running-config | include udp' to see if UDP-based services are enabledAffected if IPv4 UDP services are active and the device is processing UDP traffic on any interface
-
Verify ESP processor statusRun 'show platform' or 'show hardware' commands to confirm the Embedded Services Processor (ESP) is present and activeAffected if ESP is present and version 2.2.1/2.2.2 is running - the crash only occurs on the ESP
A user is affected if they are running Cisco IOS XE version 2.2.1 or 2.2.2 on an ASR 1000 series device with active IPv4 UDP traffic processing.
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 version 2.2.3 or later on affected ASR 1000 devices. If immediate upgrade is not possible, consider implementing ACLs to limit untrusted UDP traffic reaching the device until the upgrade can be scheduled.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6268 — 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-6268 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