Ios XeOperating system · Cisco
CVE-2015-0710
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 Overlay Transport Virtualization (OTV) implementation in Cisco IOS XE 3.10S allows remote attackers to cause a denial of service (device reload) via a series of packets that are considered oversized and trigger improper fragmentation handling, aka Bug IDs CSCup37676 and CSCup30335.
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 confidenceThe vulnerability exists in Cisco IOS XE 3.10S Overlay Transport Virtualization (OTV) implementation. Remote attackers can send oversized packets that trigger improper fragmentation handling, causing the affected device to reload and result in 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
Ios XeOperating system
= 3.10.0s= 3.10s.01CVSS 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
- Adjacent
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:A/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.
-
Identify the Cisco IOS XE versionRun 'show version' or 'show running-config | include version' to obtain the installed IOS XE software versionAffected if The version displayed is 3.10.0s or 3.10s.01 (exact match to affected versions)
-
Confirm the device is running IOS XECheck the output from 'show version' for 'IOS XE' in the software designationAffected if The software is identified as Cisco IOS XE (not classic IOS or NX-OS)
-
Verify OTV feature is enabledRun 'show feature | include otv' or check running configuration for 'otv' related commandsAffected if Overlay Transport Virtualization feature is enabled or OTV is configured on any interface
-
Check OTV interface configurationRun 'show run | include otv' or 'show otv interface' to list active OTV configurationsAffected if OTV overlay or adjacency interfaces are configured and active
-
Inspect OTV-facing network segmentsReview OTV configuration for neighbor devices and which networks are permitted in the OTV domainAffected if OTV is exposed to untrusted network segments (any OTV-facing interface not on isolated management segments)
A device is affected if it runs IOS XE versions 3.10.0s or 3.10s.01 AND has OTV feature enabled with active OTV configuration, exposing it to oversized packet attacks.
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 dataApply Cisco IOS XE software updates that address CSCup37676 and CSCup30335; as an interim measure, restrict or monitor OTV-facing network segments to reduce exposure to malformed packets.
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-0710 — 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-0710 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