dbcve.org
Adaptive Security Appliance SoftwareOperating system · Cisco

CVE-2015-0578

MEDIUM · 5.7 CVSS v2.0 Published 2015-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 Adaptive Security Appliance (ASA) Software, when a DHCPv6 relay is configured, allows remote attackers to cause a denial of service (device reload) via crafted DHCP packets on the local network, aka Bug ID CSCur45455.

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 ASA Software exists when DHCPv6 relay is enabled. Remote attackers on the local network can send specially crafted DHCPv6 packets that cause the ASA device to reload, resulting in service disruption.

MitigationIf DHCPv6 relay is not required, disable the feature. Otherwise, apply the Cisco security patch for bug ID CSCur45455. Consider network segmentation to restrict DHCPv6 packet access to trusted segments.

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
Adaptive Security Appliance SoftwareOperating 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
Adjacent
Complexity
M
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:A/AC:M/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. Confirm Cisco ASA device is in use
    Run 'show version' or 'show inventory' and look for 'Adaptive Security Appliance' or 'ASA' in the output
    Affected if The device is NOT a Cisco ASA appliance - this CVE only affects Cisco ASA Software
  2. Identify the ASA software version
    Run 'show version' and locate the 'Software Version' or 'flash:' line indicating the ASA version number
    Affected if All versions of Cisco ASA Software are affected according to the advisory
  3. Verify DHCPv6 relay is configured
    Run 'show running-config | include dhcpv6' or 'show run | grep -i dhcpv6' to check if any DHCPv6 relay commands exist in the configuration
    Affected if No DHCPv6 relay configuration found - the device may not be vulnerable if the feature is not enabled
  4. Confirm DHCPv6 relay is enabled and active
    Run 'show service-policy interface' or check the specific interface configuration with 'show run interface <if>' and look for 'dhcpv6 relay enable' under the relevant interface(s)
    Affected if DHCPv6 relay is NOT enabled on any interface - the device is not vulnerable when the feature is disabled
  5. Check for ACLs or filters restricting DHCPv6 traffic
    Review access-lists applied to interfaces with 'show access-list' and examine whether DHCPv6 traffic (port 546/547) is explicitly permitted or blocked from untrusted segments
    Affected if There are NO network filters preventing DHCPv6 packets from untrusted network segments reaching the ASA

The environment is affected if the device runs Cisco ASA Software with DHCPv6 relay enabled, allowing uncontrolled DHCPv6 packets from the local network to reach the ASA.

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

If DHCPv6 relay is not required, disable the feature. Otherwise, apply the Cisco security patch for bug ID CSCur45455. Consider network segmentation to restrict DHCPv6 packet access to trusted segments.

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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