iOSOperating system · Cisco
CVE-2013-6705
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 IP Device Tracking (IPDT) feature in Cisco IOS and IOS XE allows remote attackers to cause a denial of service (IPDT AVL corruption and device reload) via a crafted sequence of ARP packets, aka Bug ID CSCuh38133.
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 IP Device Tracking (IPDT) feature in Cisco IOS and IOS XE contains a vulnerability where remote attackers can send a crafted sequence of ARP packets causing AVL (Adelson-Velskii and Landis) tree corruption in the IPDT data structure, leading to device reload and denial of service. The attack requires no authentication and can be executed remotely over the network.
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
iOSOperating system
all versions
Ios XeOperating system
all versionsCVSS 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.
-
Check if IP Device Tracking is enabled in the configurationExecute 'show running-config | include ip device tracking' or 'show running-config all | include ip device tracking' to see if IPDT is configuredAffected if The command returns configuration lines with 'ip device tracking' (enabled) rather than 'no ip device tracking' (disabled)
-
Verify IPDT feature status using the show commandExecute 'show ip device tracking' to display the IP device tracking table status and configurationAffected if The output shows active tracking entries or 'IP Device Tracking is enabled' - indicating the feature is active and potentially vulnerable
-
Check for IPDT-related processes in memoryExecute 'show processes | include Device' or 'show ip device tracking statistics' if available to see if IPDT process is runningAffected if The command returns active IPDT processes or statistics, confirming the feature is loaded and running
-
Identify the Cisco IOS or IOS XE versionExecute 'show version' and note the IOS/IOS XE version numberAffected if All versions of Cisco IOS and IOS XE are affected; any version running with IPDT enabled is vulnerable
A device is affected if it is running any version of Cisco IOS or IOS XE with the IP Device Tracking (IPDT) feature enabled in the configuration.
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 the Cisco IOS/IOS XE software update addressing CVE-2013-6705 (Bug ID CSCuh38133). If immediate patching is not possible, consider disabling IPDT feature if not required, or implementing network segmentation to limit exposure to untrusted ARP traffic.
Fix this in iOS
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6705 — 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-2013-6705 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