dbcve.org
AsaApplication · Cisco

CVE-2014-3386

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 GPRS Tunneling Protocol (GTP) inspection engine in Cisco ASA Software 8.2 before 8.2(5.51), 8.4 before 8.4(7.15), 8.7 before 8.7(1.13), 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 series of GTP packets, aka Bug ID CSCum56399.

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

The GPRS Tunneling Protocol (GTP) inspection engine in Cisco ASA Software contains a vulnerability where specially crafted GTP packets can cause the device to reload, resulting in denial of service. The issue affects multiple version branches (8.2, 8.4, 8.7, 9.0, 9.1) prior to specific patched releases.

MitigationUpgrade Cisco ASA Software to version 8.2(5.51), 8.4(7.15), 8.7(1.13), 9.0(4.8), 9.1(5.1) or later. If GTP inspection cannot be immediately disabled during upgrade planning, consider implementing traffic filtering at upstream network edges to drop malformed GTP 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
AsaApplication
Affected:= 8.2.5= 8.2.5.13= 8.2.5.22= 8.2.5.26= 8.2.5.33= 8.2.5.41= 8.2.5.46= 8.2.5.48= 8.2.5.49= 8.4= 8.4.1= 8.4.2

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 software version
    Execute the 'show version' command on the ASA CLI to display the installed software version number.
    Affected if Version matches 8.2.5, 8.2.5.13, 8.2.5.22, 8.2.5.26, 8.2.5.33, 8.2.5.41, 8.2.5.46, 8.2.5.48, 8.2.5.49, 8.4, 8.4.1, 8.4.2 or falls within the 8.2, 8.4, 8.7, 9.0, or 9.1 branches before patched releases.
  2. Confirm GTP inspection is enabled
    Execute 'show service-policy | include gtp' or examine the inspection policy map configuration via 'show run inspection' to determine if GTP inspection is active.
    Affected if GTP inspection is enabled in the service policy or inspection map.
  3. Verify affected version range
    Compare your installed version against the known vulnerable branches (8.2, 8.4, 8.7, 9.0, 9.1) prior to patched releases 8.2(5.51), 8.4(7.15), 8.7(1.13), 9.0(4.8), 9.1(5.1).
    Affected if Running an affected version AND GTP inspection is enabled.

You are affected if your Cisco ASA runs a vulnerable 8.2, 8.4, 8.7, 9.0, or 9.1 branch version AND has GTP inspection enabled in the configuration.

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.2(5.51), 8.4(7.15), 8.7(1.13), 9.0(4.8), 9.1(5.1) or later. If GTP inspection cannot be immediately disabled during upgrade planning, consider implementing traffic filtering at upstream network edges to drop malformed GTP packets.

Fix this in Asa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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