dbcve.org
AsaApplication · Cisco

CVE-2014-3384

HIGH · 7.8 CVSS v2.0 Published 2014-10-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 IKEv2 implementation in Cisco ASA Software 8.4 before 8.4(7.15), 8.6 before 8.6(1.14), 9.0 before 9.0(4.8), and 9.1 before 9.1(5.1) allows remote attackers to cause a denial of service (device reload) via a crafted packet that is sent during tunnel creation, aka Bug ID CSCum96401.

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 exists in the IKEv2 implementation of Cisco ASA Software. Remote attackers can send a specially crafted packet during IKEv2 tunnel creation, causing the affected device to reload unexpectedly. The vulnerability affects multiple version branches (8.4, 8.6, 9.0, 9.1) prior to their respective patches.

MitigationUpgrade Cisco ASA Software to version 8.4(7.15), 8.6(1.14), 9.0(4.8), 9.1(5.1) or later. Until patching is possible, consider restricting IKEv2 tunnel initiation to trusted peers via access control lists or implementing rate limiting on IKEv2 ports.

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
AsaApplication
Affected:= 8.4= 8.4.1= 8.4.2= 8.4.3= 8.4.4= 8.6= 8.6.1= 9.0= 9.1= 9.1.5

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. Determine ASA software version
    Connect to the ASA CLI and run the command 'show version' to display the installed software version. Look for the version number in the output (for example, 8.4(7.15) or 9.1(5.1)).
    Affected if The displayed version matches any of the following: 8.4, 8.4.1, 8.4.2, 8.4.3, 8.4.4, 8.6, 8.6.1, 9.0, 9.1, or 9.1.5.
  2. Confirm IKEv2 protocol is enabled
    Run the command 'show crypto ikev2' to check the IKEv2 status. Alternatively, run 'show running-config crypto ikev2' to see if IKEv2 is configured on the device.
    Affected if IKEv2 is enabled or configured on the ASA (output shows active IKEv2 sessions or IKEv2 configuration is present).
  3. Check for IKEv2 tunnel groups
    Run the command 'show running-config tunnel-group' and filter for IKEv2 tunnel groups, or use 'show crypto ikev2 sa' to display active IKEv2 security associations.
    Affected if Any IKEv2 tunnel groups exist or active IKEv2 security associations are present.
  4. Inspect IKEv2 crypto map configuration
    Run 'show running-config crypto map' and look for entries that specify IKEv2 as the protocol (such as 'crypto map <name> set ikev2' or similar IKEv2-related crypto map configurations).
    Affected if Crypto maps with IKEv2 protocol are configured on external interfaces.
  5. Verify IKEv2 is exposed on external interfaces
    Run 'show running-config interface' for each external or internet-facing interface and check for IKEv2-related crypto configurations applied, or review access-list entries permitting UDP port 500 and 4500 (IKEv2 ports).
    Affected if IKEv2 is reachable from untrusted networks (UDP 500/4500 are permitted on external interfaces).

A device is affected if it runs any of the listed vulnerable versions (8.4, 8.4.1-8.4.4, 8.6, 8.6.1, 9.0, 9.1, 9.1.5) AND has IKEv2 enabled or configured.

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

Upgrade Cisco ASA Software to version 8.4(7.15), 8.6(1.14), 9.0(4.8), 9.1(5.1) or later. Until patching is possible, consider restricting IKEv2 tunnel initiation to trusted peers via access control lists or implementing rate limiting on IKEv2 ports.

Fix this in Asa Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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