A vulnerability in the syslog processing engine of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability is due to a race condition that may occur when syslog messages are processed. An attacker could exploit this vulnerability by sending a high rate of syslog messages to an affected device. A successful exploit could allow the attacker to cause the Application Server process to crash, resulting in a DoS condition.
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Identity_services_engine | Cisco | 2.2.0.470 (including) | 2.2.0.470 (including) |
| Identity_services_engine | Cisco | 2.2.0.470-patch1 (including) | 2.2.0.470-patch1 (including) |
| Identity_services_engine | Cisco | 2.2.0.470-patch10 (including) | 2.2.0.470-patch10 (including) |
| Identity_services_engine | Cisco | 2.2.0.470-patch11 (including) | 2.2.0.470-patch11 (including) |
| Identity_services_engine | Cisco | 2.2.0.470-patch12 (including) | 2.2.0.470-patch12 (including) |
| Identity_services_engine | Cisco | 2.2.0.470-patch2 (including) | 2.2.0.470-patch2 (including) |
| Identity_services_engine | Cisco | 2.2.0.470-patch3 (including) | 2.2.0.470-patch3 (including) |
| Identity_services_engine | Cisco | 2.2.0.470-patch4 (including) | 2.2.0.470-patch4 (including) |
| Identity_services_engine | Cisco | 2.2.0.470-patch5 (including) | 2.2.0.470-patch5 (including) |
| Identity_services_engine | Cisco | 2.2.0.470-patch6 (including) | 2.2.0.470-patch6 (including) |
| Identity_services_engine | Cisco | 2.2.0.470-patch7 (including) | 2.2.0.470-patch7 (including) |
| Identity_services_engine | Cisco | 2.2.0.470-patch8 (including) | 2.2.0.470-patch8 (including) |
| Identity_services_engine | Cisco | 2.2.0.470-patch9 (including) | 2.2.0.470-patch9 (including) |
| Identity_services_engine | Cisco | 2.3.0.298 (including) | 2.3.0.298 (including) |
| Identity_services_engine | Cisco | 2.3.0.298-patch1 (including) | 2.3.0.298-patch1 (including) |
| Identity_services_engine | Cisco | 2.3.0.298-patch2 (including) | 2.3.0.298-patch2 (including) |
| Identity_services_engine | Cisco | 2.3.0.298-patch3 (including) | 2.3.0.298-patch3 (including) |
| Identity_services_engine | Cisco | 2.3.0.298-patch4 (including) | 2.3.0.298-patch4 (including) |
| Identity_services_engine | Cisco | 2.3.0.298-patch5 (including) | 2.3.0.298-patch5 (including) |
| Identity_services_engine | Cisco | 2.4.0.357 (including) | 2.4.0.357 (including) |
| Identity_services_engine | Cisco | 2.4.0.357-patch1 (including) | 2.4.0.357-patch1 (including) |
A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:
A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.