Jason Crowder

A flaw exists in the Internet Key Exchange version 2 (IKEv2) feature that may allow a remote attacker to cause a denial of service (DoS) condition. This is due to improper parsing of IKEv2 packets. An attacker could exploit this by sending crafted IKEv2 packets to an affected device. Successful exploitation of Cisco IOS Software and IOS XE Software could cause the device to reload, resulting in a DoS condition. Successful exploitation of Cisco Secure Firewall ASA Software and Secure FTD Software could lead to partial system memory exhaustion, causing instability, such as the inability to establish new IKEv2 VPN sessions. A manual reboot of the device is required to recover.

A flaw exists in the OSPF protocol that may allow an attacker with the OSPF secret key, who is adjacent to an affected device, to cause the device to reload unexpectedly, leading to a denial-of-service (DoS) condition. This issue is caused by heap corruption when parsing packets within the OSPF service. An attacker could exploit this by sending crafted packets to the OSPF service, potentially corrupting the heap and triggering the reload.

A flaw exists in the IKEv2 feature that may allow a remote attacker with valid VPN user credentials to trigger a denial-of-service (DoS) condition. This issue stems from improper handling of IKEv2 packets. An attacker could exploit this by sending specially crafted, authenticated IKEv2 packets to a vulnerable device, potentially exhausting memory and causing a reload.

A flaw exists in the OSPF protocol of Cisco Secure Firewall ASA Software and Cisco Secure FTD Software. An unauthenticated, adjacent attacker can trigger an unexpected reload of the device, leading to a denial-of-service (DoS) condition when OSPF canonicalization debug is enabled using the `debug ip ospf canon` command. This is caused by inadequate input validation when handling OSPF Link State Update (LSU) packets. An attacker could exploit this by sending specially crafted OSPF packets, potentially allowing them to write to memory outside the allocated packet data, resulting in the device reload and DoS.

Issues in the Snort 3 VBA feature allow an unauthenticated remote attacker to crash the Snort 3 Detection Engine. This occurs due to improper error checking during the decompression of VBA data. An attacker can trigger this by sending specially crafted VBA data to the engine, leading to an unexpected restart and a Denial of Service (DoS) condition.

A flaw exists in the Snort 3 Visual Basic for Applications (VBA) feature that could allow a remote, unauthenticated attacker to crash the Snort 3 Detection Engine. This is caused by insufficient error checking during VBA data decompression. An attacker could exploit this by sending specially crafted VBA data to the engine, leading to a denial of service (DoS) condition and unexpected restarts.

A flaw exists in the Snort 3 VBA feature that may allow a remote, unauthenticated attacker to crash the Snort 3 Detection Engine. This is caused by insufficient error checking during VBA data decompression. An attacker could exploit this by sending specially crafted VBA data to the engine, potentially leading to a denial-of-service (DoS) condition where the engine enters an infinite loop.

A flaw exists in the Snort 3 detection engine that may allow a remote attacker to disrupt packet inspection. This is caused by insufficient error checking during the parsing of remote procedure call (RPC) data. An attacker could exploit this by sending specially crafted RPC packets through an existing connection, potentially leading to a denial-of-service (DoS) condition as the Snort 3 Detection Engine restarts unexpectedly.

A flaw exists in the OSPF protocol implementation of the software that could allow a nearby, authorized attacker to deplete device memory, leading to a denial of service. This is caused by improper input validation when processing OSPF packets. An attacker can exploit this by sending specially crafted OSPF packets to the device. A successful exploit could exhaust memory, resulting in a denial of service condition.

A flaw exists in the IKEv2 feature that may allow a remote, unauthenticated attacker to trigger a denial-of-service (DoS) condition on a vulnerable device. This could also impact the availability of services to other devices on the network. The issue stems from a failure to release memory during IKEv2 packet processing, leading to memory exhaustion when crafted IKEv2 packets are sent to the device. A successful exploit could exhaust system resources, resulting in a DoS condition that requires manual device reloading.

A flaw exists in the Remote Access SSL VPN, HTTP management, and MUS functionality that could allow a remote, unauthenticated attacker to deplete device memory, leading to a denial of service (DoS) condition and requiring a manual reboot. This is caused by a failure to validate user-supplied input. An attacker could exploit this by transmitting specially crafted packets to the Remote Access SSL VPN server, potentially causing the device to become unresponsive.

A flaw exists in the lockdown mechanism of the software that may allow a local attacker with valid administrative credentials to execute arbitrary commands as root. The issue stems from inadequate restrictions on remediation modules when the system is in lockdown mode. Exploitation involves sending crafted input to the system command-line interface (CLI). A successful exploit could enable an attacker to run arbitrary commands or code with root privileges, even while the system is in lockdown.

A flaw exists in the Remote Access SSL VPN functionality that could allow a remote, unauthenticated attacker to cause a denial of service (DoS) condition affecting new Remote Access SSL VPN connections by exhausting device memory. This issue stems from a failure to validate user-supplied input. An attacker could exploit this by sending specially crafted packets to the Remote Access SSL VPN server, potentially causing the device web interface to become unresponsive.

A flaw exists in the IKEv2 feature that may allow a remote attacker to disrupt service availability. The issue stems from a memory leak during the processing of IKEv2 packets. An attacker could exploit this by sending specially crafted IKEv2 packets, potentially exhausting system resources and causing a denial-of-service (DoS) condition requiring a manual device reload.

A flaw exists in the OSPF protocol that may allow a nearby attacker to cause an unexpected reload of a device, leading to a denial of service. The issue stems from inadequate validation of input when handling OSPF update packets. An attacker could exploit this by sending specially crafted OSPF update packets, potentially triggering a buffer overflow and causing the device to reload. If OSPF authentication is enabled, the attacker needs to know the secret key to successfully exploit this issue.

A flaw exists in the Remote Access SSL VPN functionality that may allow a remote attacker with a valid VPN connection to deplete device memory, leading to a denial of service (DoS) condition. The issue stems from a lack of input validation, enabling an attacker to exploit the system by transmitting specially crafted packets to the Remote Access SSL VPN server. A successful exploit could force the device to reload, resulting in a DoS condition. This does not impact the management or MUS interfaces.

A flaw exists in the Snort 3 VBA feature that may allow a remote attacker to cause the Snort 3 Detection Engine to crash. This is due to improper range checking during the decompression of VBA data, which is controlled by the user. An attacker could exploit this by sending crafted VBA data to the Snort 3 Detection Engine, potentially leading to a heap data overflow and a denial-of-service (DoS) condition.

A flaw exists in the Snort 3 detection engine that may allow a remote attacker to disrupt packet inspection. This is due to insufficient validation when processing Multicast DNS fields within HTTP headers. An attacker could exploit this by sending specially crafted HTTP packets through an existing connection, potentially causing the Snort 3 Detection Engine to restart and leading to a denial-of-service (DoS) condition.

A flaw exists in the Snort 3 Detection Engine that may allow a remote attacker to disrupt packet inspection. This is due to an error in the JSTokenizer normalization logic when handling JavaScript during HTTP inspection. An attacker could exploit this by sending specially crafted HTTP packets through an existing connection. Successful exploitation could lead to a denial-of-service condition as the Snort 3 Detection Engine unexpectedly restarts. JSTokenizer is not enabled by default.

A flaw exists in the OSPF protocol implementation of the software that could allow a remote, unauthenticated attacker to disrupt service. The issue stems from improper handling of OSPF protocol packets, leading to memory corruption. An attacker can exploit this by sending specially crafted OSPF packets to a vulnerable device. Successful exploitation may cause the device to reboot, resulting in a denial of service (DoS) condition.