iOSOperating system · Cisco

CVE-2015-0586

HIGH · 7.8 CVSS v2.0 Published 2015-01-28
Fix available
A fix is available. Upgrade to after 15.3 or later.
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 Network-Based Application Recognition (NBAR) protocol implementation in Cisco IOS 15.3(100)M and earlier on Cisco 2900 Integrated Services Router (aka Cisco Internet Router) devices allows remote attackers to cause a denial of service (NBAR process hang) via IPv4 packets, aka Bug ID CSCuo73682.

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 · moderate confidence

The NBAR (Network-Based Application Recognition) protocol implementation in Cisco IOS 15.3(100)M and earlier on Cisco 2900 Integrated Services Router devices contains a vulnerability when processing specially crafted IPv4 packets. Remote attackers can send malicious IPv4 packets to trigger a denial of service condition that causes the NBAR process to hang or become unresponsive.

MitigationUpgrade Cisco IOS to a version that addresses this vulnerability (later than 15.3(100)M). If immediate patching is not feasible, consider disabling NBAR if not required for network operations, or implement network segmentation and access controls to limit exposure to untrusted IPv4 traffic.

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
Affected:<= 15.3\(100\)m

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 Cisco device model
    Log into the device and run 'show version' or 'show inventory' to confirm the hardware platform. Look for Cisco 2900 Series Integrated Services Router.
    Affected if The device is not a Cisco 2900 Series ISR (other models may have separate advisories)
  2. Check the Cisco IOS version
    Run 'show version' and locate the IOS version string (for example, 15.3(100)M). Compare it to the affected range: any version 15.3(100)M or earlier.
    Affected if The IOS version is 15.3(100)M or any earlier 15.x release (the vulnerability exists in versions up to and including 15.3(100)M)
  3. Verify NBAR is enabled
    Run 'show nbar protocol-discovery' or 'show ip nbar protocol-discovery' to check if NBAR is actively processing traffic. Also check the running configuration with 'show run | include nbar' to see if NBAR is configured.
    Affected if NBAR is enabled and configured on the device - the vulnerability only triggers when NBAR is actively processing IPv4 packets
  4. Confirm IPv4 routing is active
    Run 'show ip interface brief' to verify IPv4 interfaces are configured and up. The exploit vector is specially crafted IPv4 packets sent to the device.
    Affected if The device has IPv4 interfaces configured and is processing IPv4 traffic - this is required for the denial of service condition to be triggered

You are affected if you are running Cisco IOS 15.3(100)M or earlier on a Cisco 2900 ISR with NBAR enabled and IPv4 interfaces active, as the vulnerability requires NBAR to process malicious IPv4 packets.

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
Upgrade available Upgrade to a release after 15.3
Interim mitigation

Upgrade Cisco IOS to a version that addresses this vulnerability (later than 15.3(100)M). If immediate patching is not feasible, consider disabling NBAR if not required for network operations, or implement network segmentation and access controls to limit exposure to untrusted IPv4 traffic.

Fix this in iOS Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0586 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-0586 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