dbcve.org
Adaptive Security Appliance SoftwareOperating system · Cisco

CVE-2013-1149

HIGH · 7.8 CVSS v2.0 Published 2013-04-11
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
Cisco Adaptive Security Appliances (ASA) devices with software 7.x before 7.2(5.10), 8.0 before 8.0(5.28), 8.1 and 8.2 before 8.2(5.35), 8.3 before 8.3(2.34), 8.4 before 8.4(4.11), 8.6 before 8.6(1.10), and 8.7 before 8.7(1.3), and Cisco Firewall Services Module (FWSM) software 3.1 and 3.2 before 3.2(24.1) and 4.0 and 4.1 before 4.1(11.1), allow remote attackers to cause a denial of service (device reload) via a crafted IKEv1 message, aka Bug IDs CSCub85692 and CSCud20267.

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

This vulnerability allows remote attackers to cause a denial of service on Cisco ASA devices and FWSM by sending a crafted IKEv1 message. The malformed IKEv1 packet triggers a fault in the device's IKE processing code, causing an immediate device reload. The attack requires no authentication and can be executed remotely over the network.

MitigationUpgrade Cisco ASA software to the specified fixed versions (7.2(5.10), 8.0(5.28), 8.2(5.35), 8.3(2.34), 8.4(4.11), 8.6(1.10), 8.7(1.3) or later) and FWSM to 3.2(24.1)/4.1(11.1) or later. Consider implementing access controls on IKE (UDP port 500) to limit which IP addresses can initiate IKE connections.

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
Affected:= 7.0= 7.0\(0\)= 7.0\(1\)= 7.0\(2\)= 7.0\(4\)= 7.0\(5\)= 7.0\(5.2\)= 7.0\(6\)= 7.0\(6.7\)= 7.0\(7\)= 7.0\(8\)= 7.0.1
5500 Series Adaptive Security ApplianceHardware / appliance
Affected:all versions
6500 Series Adaptive Security ApplianceHardware / appliance
Affected:all versions
7600 Series Adaptive Security ApplianceHardware / appliance
Affected:all versions
Firewall Services Module SoftwarePlugin / extension
Affected:= 3.1= 3.2= 3.2\(1\)= 3.2\(2\)= 3.2\(3\)= 3.2\(4\)= 3.2\(5\)= 3.2\(6\)= 3.2\(7\)= 3.2\(8\)= 3.2\(9\)= 3.2\(10\)

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 Cisco device type
    Log into the device and run 'show version' or check the device model in the running configuration. Look for ASA, Adaptive Security Appliance, or FWSM in the output.
    Affected if The device is a Cisco ASA or Firewall Services Module (FWSM)
  2. Check the installed ASA software version
    Run 'show version' on the ASA and locate the version number in the output (for example: 'Cisco ASA Software Version 7.0(5)'). Compare this version against the affected ranges: 7.0, 7.0(0), 7.0(1), 7.0(2), 7.0(4), 7.0(5), 7.0(5.2), 7.0(6), 7.0(6.7), 7.0(7), 7.0(8), 7.0.1. Also note that all versions of Cisco 5500, 6500, and 7600 Series ASA are affected.
    Affected if The ASA version is any of the listed 7.0.x versions, or the device is a 5500/6500/7600 Series ASA at any version
  3. Check the installed FWSM version
    If the device is an FWSM, run 'show version' and identify the software version. Compare against affected versions: 3.1, 3.2, 3.2(1), 3.2(2), 3.2(3), 3.2(4), 3.2(5), 3.2(6), 3.2(7), 3.2(8), 3.2(9), 3.2(10).
    Affected if The FWSM version matches any of the listed 3.1 or 3.2.x versions
  4. Verify IKEv1 is enabled on the device
    Run 'show running-config | include isakmp' or 'show crypto isakmp sa' to check for active IKEv1 configuration. IKEv1 is typically enabled by default on ASA when VPN features are configured.
    Affected if IKEv1 is enabled or any IKEv1 crypto maps/ISAKMP policies are configured

The device is affected if it is a Cisco ASA (specific 7.0.x versions or any 5500/6500/7600 series) or FWSM (specific 3.1/3.2.x versions) AND IKEv1 is enabled or could be initiated from the network.

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 the specified fixed versions (7.2(5.10), 8.0(5.28), 8.2(5.35), 8.3(2.34), 8.4(4.11), 8.6(1.10), 8.7(1.3) or later) and FWSM to 3.2(24.1)/4.1(11.1) or later. Consider implementing access controls on IKE (UDP port 500) to limit which IP addresses can initiate IKE connections.

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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