A vulnerability in the internal packet-processing functionality of the Cisco StarOS operating system running on virtual platforms 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 a logic error that may occur under specific traffic conditions. An attacker could exploit this vulnerability by sending a series of crafted packets to an affected device. A successful exploit could allow the attacker to prevent the targeted service interface from receiving any traffic, which would lead to a DoS condition on the affected interface. The device may have to be manually reloaded to recover from exploitation of this vulnerability.
The product accesses or uses a pointer that has not been initialized.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Staros | Cisco | 21.6 (including) | 21.6.13 (excluding) |
Staros | Cisco | 21.6b (including) | 21.6b.16 (excluding) |
Staros | Cisco | 21.7 (including) | 21.7.11 (excluding) |
Staros | Cisco | 21.8 (including) | 21.8.10 (excluding) |
Staros | Cisco | 21.9 (including) | 21.9.7 (excluding) |
Staros | Cisco | 21.10 (including) | 21.10.2 (excluding) |
Staros | Cisco | 21.11 (including) | 21.11.1 (excluding) |
If the pointer contains an uninitialized value, then the value might not point to a valid memory location. This could cause the product to read from or write to unexpected memory locations, leading to a denial of service. If the uninitialized pointer is used as a function call, then arbitrary functions could be invoked. If an attacker can influence the portion of uninitialized memory that is contained in the pointer, this weakness could be leveraged to execute code or perform other attacks. Depending on memory layout, associated memory management behaviors, and product operation, the attacker might be able to influence the contents of the uninitialized pointer, thus gaining more fine-grained control of the memory location to be accessed.