dbcve.org
Ios XeOperating system · Cisco

CVE-2015-0637

HIGH · 7.8 CVSS v2.0 Published 2015-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The Autonomic Networking Infrastructure (ANI) implementation in Cisco IOS 12.2, 12.4, 15.0, 15.2, 15.3, and 15.4 and IOS XE 3.10.xS through 3.13.xS before 3.13.1S allows remote attackers to cause a denial of service (device reload) via spoofed AN messages, aka Bug ID CSCup62315.

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 confidence

A vulnerability in Cisco IOS and IOS XE allows remote attackers to send spoofed Autonomic Networking (AN) messages that cause affected devices to reload, resulting in denial of service. The issue exists in the ANI implementation across multiple IOS versions (12.2 through 15.4) and IOS XE versions 3.10.xS through 3.12.xS.

MitigationUpgrade to IOS XE 3.13.1S or later; for older IOS versions, apply vendor-provided patches or consider disabling Autonomic Networking features if not required, and implement network segmentation to limit exposure to unauthenticated AN messages.

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
Affected:= 3.10s.0= 3.10s.1= 3.10s.2= 3.10s.3= 3.10s.4= 3.11s.0= 3.11s.1= 3.11s.2= 3.11s.3= 3.12s.0= 3.12s.1= 3.12s.2
iOSOperating system
Affected:= 12.2\(33\)ird1= 12.2\(33\)ire3= 12.2\(33\)sxi4b= 12.2\(44\)sq1= 12.4\(25e\)jam1= 12.4\(25e\)jap1m= 12.4\(25e\)jaz1= 15.0\(2\)ed1= 15.2\(1\)ex= 15.2\(2\)jb1= 15.3\(2\)s2= 15.3\(3\)ja1n

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device OS and version
    Run 'show version' or 'show ios version' on the Cisco device to obtain the exact OS type (IOS or IOS XE) and version number
    Affected if The device runs Cisco IOS version 12.2 through 15.4, or Cisco IOS XE version 3.10.xS through 3.12.xS, matching the specific versions listed in the affected products
  2. Verify Autonomic Networking feature is enabled
    Run 'show autonomic' or check the running configuration for 'autonomic' related commands, and inspect the device for any ANI (Autonomic Networking Infrastructure) configuration
    Affected if Autonomic Networking or ANI feature is configured and enabled on the device
  3. Confirm ANI process is running
    Run 'show process cpu | include autonomic' or 'show processes | grep -i autonomic' to see if the ANI process is actively running
    Affected if The ANI process is actively running on the device

A device is affected if it runs a vulnerable Cisco IOS (12.2-15.4) or IOS XE (3.10.xS-3.12.xS) version AND has Autonomic Networking/ANI feature enabled and running.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to IOS XE 3.13.1S or later; for older IOS versions, apply vendor-provided patches or consider disabling Autonomic Networking features if not required, and implement network segmentation to limit exposure to unauthenticated AN messages.

Fix this in Ios Xe Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0637 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-0637 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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