CVE-2018-0228

HIGH
8.6
CVSS Score
Published: April 19, 2018 at 08:00 PM UTC
Updated: August 11, 2026 at 07:37 PM UTC
2 products affected across 1 vendorAdaptive Security ApplianceSecure Firewall Threat Defense

Using Cisco Adaptive Security Appliance by N/A?

Get instant alerts when new vulnerabilities affect Cisco Adaptive Security Appliance - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.6
Exploit prediction
EPSS 4%
SSVC
No known exploit

Description

A vulnerability in the ingress flow creation functionality of Cisco Adaptive Security Appliance (ASA) could allow an unauthenticated, remote attacker to cause the CPU to increase upwards of 100% utilization, causing a denial of service (DoS) condition on an affected system. The vulnerability is due to incorrect handling of an internal software lock that could prevent other system processes from getting CPU cycles, causing a high CPU condition. An attacker could exploit this vulnerability by sending a steady stream of malicious IP packets that can cause connections to be created on the targeted device. A successful exploit could allow the attacker to exhaust CPU resources, resulting in a DoS condition during which traffic through the device could be delayed. This vulnerability applies to either IPv4 or IPv6 ingress traffic. This vulnerability affects Cisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD) Software that is running on the following Cisco products: 3000 Series Industrial Security Appliances (ISA), ASA 5500 Series Adaptive Security Appliances, ASA 5500-X Series Next-Generation Firewalls, ASA Services Module for Cisco Catalyst 6500 Series Switches and Cisco 7600 Series Routers, Adaptive Security Virtual Appliances (ASAv), Firepower 2100 Series Security Appliances, Firepower 4110 Security Appliances, Firepower 9300 ASA Security Modules. Cisco Bug IDs: CSCvf63718.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

9.1 ≤ v < 9.1.7.209.2 ≤ v < 9.2.4.279.3 ≤ v < 9.4.4.139.5 ≤ v < 9.6.3.179.7 ≤ v < 9.7.1.169.8 ≤ v < 9.8.2.149.9 ≤ v < 9.9.198.1(12.187)
Affected range stops below 9.1.7.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.2.4.27, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.4.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.6.3.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.7.1.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.8.2.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.9.1, so it looks safe — our inference, not a vendor statement
6.0 ≤ v < 6.1.0.66.2.0 ≤ v < 6.2.0.56.2.1 ≤ v < 6.2.2.2

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (4)

VDB Entryx_refsource_BIDThird Party Advisory
http://www.securityfocus.com/bid/104220
VDB Entryx_refsource_SECTRACKThird Party Advisory
http://www.securitytracker.com/id/1040724
x_refsource_MISCThird Party AdvisoryUS Government Resource
https://ics-cert.us-cert.gov/advisories/ICSA-18-184-01

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-20CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card