dbcve.org
AsaApplication · Cisco

CVE-2014-3383

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 IKE implementation in the VPN component in Cisco ASA Software 9.1 before 9.1(5.1) allows remote attackers to cause a denial of service (device reload) via crafted UDP packets, aka Bug ID CSCul36176.

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 IKE (Internet Key Exchange) implementation within the VPN component of Cisco ASA Software version 9.1 before 9.1(5.1). Remote attackers can trigger the vulnerability by sending specially crafted UDP packets to the affected ASA device, causing an unexpected device reload.

MitigationUpgrade Cisco ASA Software to version 9.1(5.1) or later to remediate this vulnerability. If immediate upgrade is not feasible, consider implementing IPsec ACLs to restrict IKE traffic to trusted VPN peers only.

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:= 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. Identify Cisco ASA device and firmware version
    Run 'show version' on the ASA CLI to display the installed software version. Look for the version number in the output.
    Affected if The displayed version is 9.1.x where x is less than 5.1 (for example, 9.1, 9.1(1), 9.1(5))
  2. Confirm IKE VPN feature is enabled
    Run 'show running-config crypto ikev1' and 'show running-config crypto ikev2' to check if IKE is configured.
    Affected if Output shows IKEv1 or IKEv2 configuration entries, indicating the IKE feature is active
  3. Verify VPN interface configuration
    Run 'show running-config | include crypto' to check which interfaces have crypto (VPN) features enabled.
    Affected if Interfaces are configured with crypto map or VPN settings, exposing the IKE service to network traffic
  4. Check device accessibility on IKE port
    Verify UDP port 500 is open to the ASA from untrusted networks using 'show asp drop' or network scanning tools.
    Affected if UDP port 500 is accessible from external or untrusted networks, allowing attackers to send malicious IKE packets

The device is affected if it runs Cisco ASA Software version 9.1 through 9.1(5) with IKE VPN enabled and exposed to network access on UDP port 500.

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 9.1(5.1) or later to remediate this vulnerability. If immediate upgrade is not feasible, consider implementing IPsec ACLs to restrict IKE traffic to trusted VPN peers only.

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