dbcve.org
iOSOperating system · Cisco

CVE-2015-0598

MEDIUM · 6.8 CVSS v2.0 Published 2015-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable 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 RADIUS implementation in Cisco IOS and IOS XE allows remote attackers to cause a denial of service (device reload) via crafted IPv6 Attributes in Access-Accept packets, aka Bug IDs CSCur84322 and CSCur27693.

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 RADIUS implementation in Cisco IOS and IOS XE contains a vulnerability where crafted IPv6 Attributes in RADIUS Access-Accept packets can trigger a denial of service, causing the affected device to reload. The attack is remote and requires no authentication.

MitigationApply the appropriate Cisco IOS/IOS XE software updates from the Cisco Security Advisory. Until patched, consider filtering or rate-limiting untrusted RADIUS traffic at network boundaries and implementing access controls on the RADIUS infrastructure.

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:all versions
Ios XeOperating system
Affected:all versions

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
Single
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:S/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
    Execute 'show version' or 'show version | include IOS' on the device CLI to confirm it runs Cisco IOS or Cisco IOS XE
    Affected if The device runs Cisco IOS or Cisco IOS XE of any version - all versions are affected per the advisory
  2. Determine if RADIUS is configured
    Execute 'show running-config | include radius' or 'show running-config | include aaa.*group.*server.*radius' to check for RADIUS server configuration
    Affected if RADIUS server configuration is present in the running configuration
  3. Verify RADIUS is enabled for network authentication
    Execute 'show aaa server' or 'show aaa method-list' to confirm RADIUS is active as an authentication/authorization method
    Affected if RADIUS is enabled as an active AAA method (authentication, authorization, or accounting)
  4. Confirm IPv6 is enabled on the device
    Execute 'show ip6 interface brief' or check 'show running-config | include ip routing' to see if IPv6 is operational
    Affected if IPv6 is enabled and operational on the device - the vulnerable IPv6 Attributes in RADIUS packets require IPv6 to be present

The device is affected if it runs Cisco IOS or IOS XE, has RADIUS configured and enabled, and has IPv6 enabled - the combination of these three conditions means crafted IPv6 Attributes in RADIUS Access-Accept packets can trigger a reload.

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

Apply the appropriate Cisco IOS/IOS XE software updates from the Cisco Security Advisory. Until patched, consider filtering or rate-limiting untrusted RADIUS traffic at network boundaries and implementing access controls on the RADIUS infrastructure.

Fix this in iOS Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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