dbcve.org
Ios XeOperating system · Cisco

CVE-2015-0708

MEDIUM · 6.1 CVSS v2.0 Published 2015-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
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
Cisco IOS 15.4S, 15.4SN, and 15.5S and IOS XE 3.13S and 3.14S allow remote attackers to cause a denial of service (device crash) by including an IA_NA option in a DHCPv6 Solicit message on the local network, aka Bug ID CSCur29956.

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 denial of service vulnerability in Cisco IOS 15.4S/15.4SN/15.5S and IOS XE 3.13S/3.14S allows remote attackers on the local network to crash affected devices by sending DHCPv6 Solicit messages containing an IA_NA (Identity Association for Non-Temporary Addresses) option. The vulnerability stems from improper handling of this specific DHCPv6 option during packet processing.

MitigationApply the relevant Cisco security patch or upgrade to a fixed IOS/IOS XE version. If DHCPv6 is not required, consider disabling it to reduce attack surface. Restrict local network access to trusted hosts to limit exposure.

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.13s.0= 3.13s.1= 3.14s.0
iOSOperating system
Affected:= 15.4\(3\)s= 15.4\(3\)s1= 15.4\(3\)sn1= 15.4s= 15.4sn= 15.5\(1\)s= 15.5s

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
Adjacent
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:A/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 IOS or IOS XE version
    Run the command 'show version' on the device and locate the version string in the output. Look for patterns such as 'Version 15.4(3)S', 'Version 15.4(3)S1', 'Version 15.4(3)SN1', 'Version 15.5(1)S', or 'Version 3.13S', 'Version 3.14S'.
    Affected if The installed version matches one of the affected versions: 15.4(3)s, 15.4(3)s1, 15.4(3)sn1, 15.4s, 15.4sn, 15.5(1)s, 15.5s for iOS, or 3.13s.0, 3.13s.1, 3.14s.0 for IOS XE.
  2. Verify DHCPv6 is configured on the device
    Run 'show running-config | include dhcpv6' or 'show ipv6 dhcp interface' to see if DHCPv6 is enabled anywhere in the configuration.
    Affected if DHCPv6 is actively configured on one or more interfaces, meaning the device will process incoming DHCPv6 messages.
  3. Confirm DHCPv6 is active on specific interfaces
    Run 'show ip interface brief' or 'show ipv6 interface' to list all interfaces with IPv6 and DHCPv6 enabled. Check the output for interfaces in 'up' state with DHCPv6 pool or relay configured.
    Affected if Any interface is 'up' with DHCPv6 processing enabled, making it reachable by local network attackers sending malicious DHCPv6 Solicit messages.
  4. Check for IA_NA option handling exposure
    Review the device configuration for any DHCPv6 prefix delegation or address assignment pools using 'show ipv6 dhcp pool' or by examining the running-config for 'ipv6 dhcp pool' entries.
    Affected if The device uses DHCPv6 pools for IA_NA address assignment, confirming it processes the vulnerable IA_NA option in DHCPv6 messages.

The device is affected if it runs any of the listed affected iOS or IOS XE versions AND has DHCPv6 enabled with IA_NA processing active on any interface reachable by local network attackers.

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 relevant Cisco security patch or upgrade to a fixed IOS/IOS XE version. If DHCPv6 is not required, consider disabling it to reduce attack surface. Restrict local network access to trusted hosts to limit exposure.

Fix this in Ios Xe 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 help mitigating

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