Ios XeOperating system · Cisco
CVE-2015-0644
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 · uneditedAppNav in Cisco IOS XE 3.8 through 3.10 before 3.10.3S, 3.11 before 3.11.3S, 3.12 before 3.12.1S, 3.13 before 3.13.0S, 3.14 before 3.14.0S, and 3.15 before 3.15.0S allows remote attackers to execute arbitrary code or cause a denial of service (device reload) via a crafted TCP packet, aka Bug ID CSCuo53622.
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 confidenceA remote code execution and denial of service vulnerability exists in Cisco IOS XE's AppNav feature across versions 3.8 through 3.15. The flaw allows unauthenticated remote attackers to send specially crafted TCP packets to trigger memory corruption, potentially executing arbitrary code or causing device reload.
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.8s.0= 3.8s.1= 3.8s.2= 3.8s_base= 3.9s.0= 3.9s.1= 3.9s.2= 3.10s.0= 3.10s.0a= 3.10s.1= 3.10s.2= 3.11s.0CVSS 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.
-
Identify the Cisco IOS XE versionRun 'show version' on the device CLI and locate the IOS XE release line (typically shows as 'Version 3.x.xS' or similar)Affected if The installed version matches one of the affected builds listed (3.8s.0 through 3.11s.0) or is earlier than the fixed releases (3.10.3S, 3.11.3S, 3.12.1S, 3.13.0S, 3.14.0S, 3.15.0S)
-
Confirm AppNav feature is configuredRun 'show appnav status' or 'show running-config | include appnav' to determine if the AppNav feature is enabled on the deviceAffected if AppNav is enabled and the IOS XE version falls within the affected range
-
Verify management interface exposureReview the device configuration for exposed management interfaces (HTTP, HTTPS, Telnet, SSH) that accept traffic from untrusted networks using 'show ip interface brief' and review access control listsAffected if Management interfaces are accessible from untrusted networks while running a vulnerable IOS XE version with AppNav enabled
The device is affected if it runs Cisco IOS XE versions 3.8s through 3.11s (or any version earlier than the fixed releases 3.10.3S/3.11.3S/3.12.1S/3.13.0S/3.14.0S/3.15.0S) AND has the AppNav feature enabled with exposed management interfaces.
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 relevant Cisco IOS XE software update (3.10.3S, 3.11.3S, 3.12.1S, 3.13.0S, 3.14.0S, or 3.15.0S) as specified in the Cisco advisory. If immediate patching is not feasible, restrict network access to the affected device's management interfaces.
Fix this in Ios Xe
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0644 — 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-0644 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