SRX Series and MX Series with SPC3: A high percentage of fragments might lead to high latency or packet drops
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 18.2R3, 18.3R3, 18.4R2-S9, 18.4R3 and 2 more.
An Insufficient Algorithmic Complexity combined with an Allocation of Resources Without Limits or Throttling vulnerability in the flow processing daemon (flowd) of Juniper Networks Junos OS on SRX Series and MX Series with SPC3 allows an unauthenticated network attacker to cause latency in transit packet processing and even packet loss. If transit traffic includes a significant percentage (> 5%) of fragmented packets which need to be reassembled, high latency or packet drops might be observed. This issue affects Juniper Networks Junos OS on SRX Series, MX Series with SPC3: All versions prior to 18.2R3; 18.3 versions prior to 18.3R3; 18.4 versions prior to 18.4R2-S9, 18.4R3; 19.1 versions prior to 19.1R2; 19.2 versions prior to 19.2R1-S1, 19.2R2.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Juniper Networks | <18.2R3, >=18.3 <18.3R3, >=18.4 <18.4R2-S9, 18.4R3, >=19.1 <19.1R2, >=19.2 <19.2R1-S1, 19.2R2 | 18.2R3, 18.3R3, 18.4R2-S9, 18.4R3, 19.1R2, 19.2R1-S1, 19.2R2 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket