A Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition) vulnerability in the Flow-processing Daemon (flowd) of Juniper Networks Junos OS on SRX Series allows an unauthenticated, network-based attacker to cause a Denial-of-Service (Dos).
On SRX Series devices when two different threads try to simultaneously process a queue which is used for TCP events flowd will crash. One of these threads can not be triggered externally, so the exploitation of this race condition is outside the attackers direct control.
Continued exploitation of this issue will lead to a sustained DoS.
This issue affects Juniper Networks Junos OS:
This issue does not affect Juniper Networks Junos OS versions earlier than 21.2R1.
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 |
|---|---|---|---|
| Junos | Juniper | 21.2 (including) | 21.2 (including) |
| Junos | Juniper | 21.2-r1 (including) | 21.2-r1 (including) |
| Junos | Juniper | 21.2-r1-s1 (including) | 21.2-r1-s1 (including) |
| Junos | Juniper | 21.2-r1-s2 (including) | 21.2-r1-s2 (including) |
| Junos | Juniper | 21.2-r2 (including) | 21.2-r2 (including) |
| Junos | Juniper | 21.2-r2-s1 (including) | 21.2-r2-s1 (including) |
| Junos | Juniper | 21.2-r2-s2 (including) | 21.2-r2-s2 (including) |
| Junos | Juniper | 21.2-r3 (including) | 21.2-r3 (including) |
| Junos | Juniper | 21.2-r3-s1 (including) | 21.2-r3-s1 (including) |
| Junos | Juniper | 21.2-r3-s2 (including) | 21.2-r3-s2 (including) |
| Junos | Juniper | 21.2-r3-s3 (including) | 21.2-r3-s3 (including) |
| Junos | Juniper | 21.2-r3-s4 (including) | 21.2-r3-s4 (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.