dbcve.org
Adaptive Security ApplianceHardware / appliance · Cisco

CVE-2013-3382

HIGH · 7.8 CVSS v2.0 Published 2013-06-26
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 Next-Generation Firewall (aka NGFW, formerly CX Context-Aware Security) module 9.x before 9.1.1.9 and 9.1.2.x before 9.1.2.12 for Cisco Adaptive Security Appliances (ASA) devices allows remote attackers to cause a denial of service (device reload or traffic-processing outage) via fragmented (1) IPv4 or (2) IPv6 traffic, aka Bug ID CSCue88387.

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 vulnerability exists in the Next-Generation Firewall module for Cisco ASA devices. Specially crafted fragmented IPv4 or IPv6 traffic causes the device to either reload or experience a traffic-processing outage, resulting in denial of service.

MitigationApply the vendor-supplied software updates (9.1.1.9, 9.1.2.12 or later) to the ASA device. If immediate patching is not feasible, consider filtering or rate-limiting fragmented traffic at an upstream perimeter device as a temporary mitigation.

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 ApplianceHardware / appliance
Affected:= 9.1.1= 9.1.1.1= 9.1.1.2= 9.1.1.3= 9.1.1.4= 9.1.1.5= 9.1.1.6= 9.1.1.7= 9.1.1.8= 9.1.2= 9.1.2.1= 9.1.2.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 the device and obtain the ASA software version
    Run the command 'show version' on the Cisco ASA CLI. Look for the line showing 'Cisco Adaptive Security Appliance (ASA) Software' with the version number displayed.
    Affected if The displayed version matches 9.1.1 through 9.1.1.8, or 9.1.2 through 9.1.2.2 exactly (these are the affected versions listed).
  2. Confirm the device is an ASA platform
    In the 'show version' output, verify the hardware platform is identified as 'Cisco Adaptive Security Appliance' or 'ASA' series device.
    Affected if The hardware is not a Cisco ASA device - the vulnerability only affects ASA platforms.
  3. Check if the NGFW module is present and active
    Run the command 'show module' to list any installed modules such as the IPS module, FirePOWER module, or other security service modules. Also run 'show running-config | include module' to check module-related configuration.
    Affected if The vulnerability is in the Next-Generation Firewall module - if no NGFW module (IPS, FirePOWER, CX, etc.) is installed and active, the specific attack surface may not apply even on affected software versions.
  4. Verify IPv4 or IPv6 fragmented traffic can reach the ASA
    Review the ASA interface configuration with 'show running-config interface' and verify whether the affected interfaces accept fragmented traffic. Check for any input filters or ACLs that might block fragmented packets before reaching the ASA.
    Affected if Fragmented IPv4 or IPv6 traffic can reach the ASA device's interfaces - this is the traffic type that triggers the vulnerability.

You are affected if you are running a Cisco ASA with software version 9.1.1 through 9.1.1.8 or 9.1.2 through 9.1.2.2, have an NGFW/IPS module installed, and accept fragmented IPv4/IPv6 traffic on the device.

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

Apply the vendor-supplied software updates (9.1.1.9, 9.1.2.12 or later) to the ASA device. If immediate patching is not feasible, consider filtering or rate-limiting fragmented traffic at an upstream perimeter device as a temporary mitigation.

Fix this in Adaptive Security Appliance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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