dbcve.org
Ios XeOperating system · Cisco

CVE-2015-0635

HIGH · 9.0 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 →
99/100
Remediation priority · Urgent
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 spoof Autonomic Networking Registration Authority (ANRA) responses, and consequently bypass intended device and node access restrictions or cause a denial of service (disrupted domain access), via crafted AN messages, aka Bug ID CSCup62191.

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

The Autonomic Networking Infrastructure (ANI) in Cisco IOS and IOS XE fails to properly validate Autonomic Networking Registration Authority (ANRA) responses, allowing remote attackers to spoof these responses via crafted AN messages. This enables bypass of device and node access restrictions or causes denial of service by disrupting domain access.

MitigationUpdate to Cisco IOS XE 3.13.1S or later. For IOS versions, Cisco has released corresponding patches. Apply compensating controls such as network segmentation and access lists to limit exposure to untrusted networks until patches can be deployed.

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.10s.5= 3.11s.0= 3.11s.1= 3.11s.2= 3.11s.3= 3.12s.0= 3.12s.1
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
Partial
Integrity
Partial
Availability
Complete

AV:N/AC:L/Au:N/C:P/I:P/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 Cisco device OS and version
    Run 'show version' on the device CLI to obtain the exact IOS or IOS XE version number
    Affected if The version matches one of the listed affected versions: IOS XE 3.10s.0-3.12s.1, or iOS 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, or 15.3(3)ja1n
  2. Determine if Autonomic Networking is enabled
    Run 'show autonomic networking' or check the running configuration for 'autonomic' related commands such as 'autonomic', 'anrp', or 'anra'
    Affected if Autonomic Networking features are configured and active on the device
  3. Verify the ANRA (Autonomic Networking Registration Authority) configuration
    Run 'show anra' or 'show autonomic networking registration authority' to check if ANRA is configured and operational
    Affected if The device is acting as an ANRA or communicating with an ANRA in the domain
  4. Check for untrusted network exposure
    Review interface configurations and access lists to determine if the device has Autonomic Networking enabled on interfaces exposed to untrusted networks
    Affected if Autonomic Networking traffic can be received from untrusted or external network segments

The device is affected if it runs a vulnerable IOS or IOS XE version listed above AND has Autonomic Networking infrastructure enabled, particularly if exposed to untrusted networks where crafted ANRA response messages could be injected.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to Cisco IOS XE 3.13.1S or later. For IOS versions, Cisco has released corresponding patches. Apply compensating controls such as network segmentation and access lists to limit exposure to untrusted networks until patches can be deployed.

Recommended fix High confidence

IOS XE 3.13.1S or later (for IOS XE); appropriate iOS fix per Cisco advisory (for iOS)

  1. 1. Identify the current Cisco IOS XE or iOS version using 'show version' command
  2. 2. Confirm the device is running an affected version (IOS XE 3.10.xS through 3.13.xS before 3.13.1S, or iOS 12.2 variants listed)
  3. 3. Schedule a maintenance window for the upgrade (this is a high-severity vulnerability allowing remote spoofing)
  4. 4. Download the fixed IOS XE release 3.13.1S or later from Cisco (for IOS XE devices), or the appropriate fixed iOS release from Cisco (for iOS devices)
  5. 5. Backup the current device configuration using 'copy running-config tftp:' or similar
  6. 6. Upload the new IOS/IOS XE image to the device using 'copy tftp flash:'
  7. 7. Configure the new boot image: 'boot system flash:<new_image_name>'
  8. 8. Reload the device using 'reload' command
Caveat Standard Cisco IOS upgrade caveats apply - review release notes for potential compatibility issues with existing features and configurations

Generated from the published advisory — verify against the referenced sources before acting.

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-0635 — 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-0635 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