Ios XeOperating system · Cisco
CVE-2015-0685
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 3.7.5S on ASR 1000 devices does not properly handle route adjacencies, which allows remote attackers to cause a denial of service (device hang) via crafted IP packets, aka Bug ID CSCub31873.
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 3.7.5S on ASR 1000 devices contains a flaw in route adjacency handling. When the device processes specially crafted IP packets, the improper handling causes the router to hang, resulting in a denial of service condition.
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.7s.4CVSS 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 an ASR 1000 series routerExecute 'show version' or 'show platform' and verify the hardware model indicated in the output is an ASR 1000 series deviceAffected if The device is not an ASR 1000 series router, then this CVE does not apply
-
Check installed Cisco IOS XE versionExecute 'show version' and locate the version string in the output (typically displayed as 'Version 15.x' or 'Version 3.xS')Affected if The displayed version is 3.7S.4 or earlier, or any version in the 3.7S.x family below 3.7.5S
-
Verify the IOS XE train identifierIn the 'show version' output, confirm the version begins with '3.7' or lower in the 3.xS train (for example, 3.7S.0 through 3.7S.4)Affected if The version string contains '3.7S' followed by a number 4 or lower, indicating it falls within the affected range
-
Confirm route adjacency processing is activeThis vulnerability affects route adjacency handling - in Cisco IOS XE, this functionality is integral to IP routing and is active by default when routing is enabled. Verify routing is enabled with 'show ip route'Affected if The device has IP routing enabled (show ip route returns active routes), meaning the vulnerable code path can be triggered by specially crafted packets
The device is affected if it is an ASR 1000 series router running Cisco IOS XE version 3.7S.4 or earlier (any version below 3.7.5S in the 3.7S train) and has IP routing functionality enabled.
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 3.7.5S or later on affected ASR 1000 devices. Prior to upgrading, schedule a maintenance window and test the new version in a non-production environment to ensure compatibility with existing configurations.
Fix this in Ios Xe
Scoped from the published advisory
- Consultation6.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0685 — 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-0685 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