CVE-2017-6663
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 · uneditedA vulnerability in the Autonomic Networking feature of Cisco IOS Software and Cisco IOS XE Software could allow an unauthenticated, adjacent attacker to cause autonomic nodes of an affected system to reload, resulting in a denial of service (DoS) condition. More Information: CSCvd88936. Known Affected Releases: Denali-16.2.1 Denali-16.3.1.
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 confidenceThis is a vulnerability in Cisco IOS and IOS XE Software's Autonomic Networking feature. An unauthenticated attacker on the adjacent network segment can exploit this flaw to cause affected devices to reload, resulting in denial of service. The attack does not require authentication but requires the attacker to be on the same network segment as the vulnerable devices.
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= 15.2\(3\)e= 15.2\(3\)e1= 15.2\(3\)e2= 15.2\(3\)e3= 15.2\(3\)e4= 15.2\(3\)e5= 15.2\(3a\)e= 15.2\(3a\)e1= 15.2\(3m\)e2= 15.2\(3m\)e3= 15.2\(3m\)e6= 15.2\(3m\)e8= 3.7.0e= 3.7.1e= 3.7.3e= 3.8.0e= 3.8.0ex= 3.8.1e= 3.8.2e= 3.8.3e= 3.9.0e= 3.9.1e= 3.10.4s= 3.10.8asCVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Determine the Cisco IOS or IOS XE versionRun 'show version' on the device CLI and locate the version string in the output (e.g., 'Version 15.2(3)e' or 'Version 03.10.04s')Affected if The displayed version matches any of the listed affected versions: 15.2(3)e through 15.2(3m)e8 for iOS, or 3.7.0e through 3.10.8as for IOS XE
-
Verify if Autonomic Networking is enabledRun 'show running-config | include autonomic' or 'show autonomic' in the device CLI to check for Autonomic Networking configurationAffected if Autonomic Networking is actively enabled or configured on the device
-
Confirm the device is reachable on the local segmentVerify network accessibility from an adjacent attacker perspective - the device must have Layer 2 adjacency with untrusted hostsAffected if The device is on a network segment where untrusted/unauthenticated hosts can directly communicate with it (same broadcast domain/VLAN)
The device is affected if it runs one of the listed vulnerable versions AND has Autonomic Networking enabled AND is exposed to adjacent network attackers.
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.
dbcve · scopedIf Autonomic Networking is not required in the environment, disable the feature. Otherwise, apply Cisco's patched software releases when available. Implement network segmentation to limit adjacent attacker access to the autonomic infrastructure.
Obtain fixed release from Cisco security advisory for CVE-2017-6663 (specific version varies by platform - check tools.cisco.com)
- 1. Identify the current Cisco IOS or IOS XE version running on the affected device using 'show version' command
- 2. Access Cisco's official security advisory for CVE-2017-6663 at tools.cisco.com to obtain the specific fixed release for your device platform
- 3. Plan maintenance window as the upgrade will require device reload
- 4. Backup current device configuration using 'copy running-config startup-config' or export via TFTP/FTP
- 5. Download the recommended fixed IOS/IOS XE release from Cisco's software center
- 6. Upgrade the device using appropriate method (TFTP, FTP, USB, or Cisco Prime Infrastructure)
- 7. After upgrade, verify the new version is installed with 'show version'
- 8. Confirm autonomic networking functionality is operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.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,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6663 — 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-2017-6663 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