Adaptive Security Appliance SoftwareOperating system · Cisco
CVE-2014-2182
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 · uneditedCisco Adaptive Security Appliance (ASA) Software, when DHCPv6 replay is configured, allows remote attackers to cause a denial of service (device reload) via a crafted DHCPv6 packet, aka Bug ID CSCun45520.
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 confidenceCisco ASA Software contains a denial-of-service vulnerability when DHCPv6 relay is configured. A remote attacker can send a crafted DHCPv6 packet to the ASA device, causing it to reload unexpectedly. The vulnerability stems from improper handling of specially malformed DHCPv6 packets.
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
all versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cisco ASA is in useIdentify the device model and verify it is a Cisco Adaptive Security Appliance. Use 'show version' or 'show inventory' commands to confirm the hardware and software.Affected if The device is not a Cisco ASA.
-
Check ASA software versionRun 'show version' on the ASA CLI to retrieve the installed Cisco ASA Software version.Affected if All versions of Cisco ASA Software are affected when DHCPv6 relay is configured.
-
Determine if DHCPv6 relay is enabledRun 'show run all dhcpv6' or 'show run | include dhcpv6' to check for any DHCPv6 relay configuration. Look for commands like 'dhcpv6 relay' or 'ipv6 dhcp relay' in the configuration.Affected if DHCPv6 relay is configured on the ASA (the device is vulnerable).
-
Check for active DHCPv6 relay bindingsRun 'show ipv6 dhcp relay statistics' or 'show dhcpv6 relay' to see if the relay service is actively running and processing packets.Affected if DHCPv6 relay service is active and processing requests.
The environment is affected only if the Cisco ASA has DHCPv6 relay configured and enabled, regardless of software version since all versions are vulnerable.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the relevant Cisco ASA software update that addresses Bug ID CSCun45520. If immediate patching is not feasible, consider disabling DHCPv6 relay if not required in the environment.
Fix this in Adaptive Security Appliance Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2182 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-2182 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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