First published: Thu Apr 19 2018(Updated: )
A vulnerability in the internal packet-processing functionality of Cisco Firepower Threat Defense (FTD) Software for Cisco Firepower 2100 Series Security Appliances could allow an unauthenticated, remote attacker to cause an affected device to stop processing traffic, resulting in a denial of service (DoS) condition. The vulnerability is due to the affected software improperly validating IP Version 4 (IPv4) and IP Version 6 (IPv6) packets after the software reassembles the packets (following IP Fragmentation). An attacker could exploit this vulnerability by sending a series of malicious, fragmented IPv4 or IPv6 packets to an affected device. A successful exploit could allow the attacker to cause Snort processes on the affected device to hang at 100% CPU utilization, which could cause the device to stop processing traffic and result in a DoS condition until the device is reloaded manually. This vulnerability affects Cisco Firepower Threat Defense (FTD) Software Releases 6.2.1 and 6.2.2, if the software is running on a Cisco Firepower 2100 Series Security Appliance. Cisco Bug IDs: CSCvf91098.
Credit: ykramarz@cisco.com ykramarz@cisco.com
Affected Software | Affected Version | How to fix |
---|---|---|
Cisco Firepower Threat Defense | =6.2.1 | |
Cisco Firepower Threat Defense | =6.2.2 | |
Cisco Adaptive Security Appliance Software | =9.8\(2\) |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-0230 is rated as a high severity vulnerability due to its potential to cause a denial of service.
To mitigate CVE-2018-0230, upgrade to the patched versions of Cisco Firepower Threat Defense or Adaptive Security Appliance Software as specified by Cisco.
CVE-2018-0230 affects Cisco Firepower Threat Defense software version 6.2.1 and 6.2.2, as well as Cisco Adaptive Security Appliance Software version 9.8(2).
Yes, CVE-2018-0230 can be exploited by an unauthenticated remote attacker.
Exploitation of CVE-2018-0230 can lead to the affected device stopping its traffic processing, resulting in service disruption.