First published: Wed Jan 19 2022(Updated: )
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.
Credit: sirt@juniper.net
Affected Software | Affected Version | How to fix |
---|---|---|
Juniper JUNOS | <18.2 | |
Juniper JUNOS | =18.2 | |
Juniper JUNOS | =18.2-r | |
Juniper JUNOS | =18.2-r1 | |
Juniper JUNOS | =18.2-r1 | |
Juniper JUNOS | =18.2-r1-s2 | |
Juniper JUNOS | =18.2-r1-s3 | |
Juniper JUNOS | =18.2-r1-s4 | |
Juniper JUNOS | =18.2-r1-s5 | |
Juniper JUNOS | =18.2-r2 | |
Juniper JUNOS | =18.2-r2-s1 | |
Juniper JUNOS | =18.2-r2-s2 | |
Juniper JUNOS | =18.2-r2-s3 | |
Juniper JUNOS | =18.2-r2-s4 | |
Juniper JUNOS | =18.2-r2-s5 | |
Juniper JUNOS | =18.2-r2-s6 | |
Juniper JUNOS | =18.2-r2-s7 | |
Juniper JUNOS | =18.2-r2-s8 | |
Juniper JUNOS | =18.3 | |
Juniper JUNOS | =18.3-r | |
Juniper JUNOS | =18.3-r1 | |
Juniper JUNOS | =18.3-r1-s1 | |
Juniper JUNOS | =18.3-r1-s2 | |
Juniper JUNOS | =18.3-r1-s3 | |
Juniper JUNOS | =18.3-r1-s4 | |
Juniper JUNOS | =18.3-r1-s5 | |
Juniper JUNOS | =18.3-r1-s6 | |
Juniper JUNOS | =18.3-r2 | |
Juniper JUNOS | =18.3-r2-s1 | |
Juniper JUNOS | =18.3-r2-s2 | |
Juniper JUNOS | =18.3-r2-s3 | |
Juniper JUNOS | =18.3-r2-s4 | |
Juniper JUNOS | =18.4 | |
Juniper JUNOS | =18.4-r1 | |
Juniper JUNOS | =18.4-r1-s1 | |
Juniper JUNOS | =18.4-r1-s2 | |
Juniper JUNOS | =18.4-r1-s3 | |
Juniper JUNOS | =18.4-r1-s4 | |
Juniper JUNOS | =18.4-r1-s5 | |
Juniper JUNOS | =18.4-r1-s6 | |
Juniper JUNOS | =18.4-r1-s7 | |
Juniper JUNOS | =18.4-r2 | |
Juniper JUNOS | =18.4-r2-s1 | |
Juniper JUNOS | =18.4-r2-s2 | |
Juniper JUNOS | =18.4-r2-s3 | |
Juniper JUNOS | =18.4-r2-s4 | |
Juniper JUNOS | =18.4-r2-s5 | |
Juniper JUNOS | =18.4-r2-s6 | |
Juniper JUNOS | =18.4-r2-s7 | |
Juniper JUNOS | =18.4-r2-s8 | |
Juniper JUNOS | =19.1 | |
Juniper JUNOS | =19.1-r1 | |
Juniper JUNOS | =19.1-r1-s1 | |
Juniper JUNOS | =19.1-r1-s2 | |
Juniper JUNOS | =19.1-r1-s3 | |
Juniper JUNOS | =19.1-r1-s4 | |
Juniper JUNOS | =19.1-r1-s5 | |
Juniper JUNOS | =19.1-r1-s6 | |
Juniper JUNOS | =19.2 | |
Juniper JUNOS | =19.2-r1 | |
Juniper Mx10 | ||
Juniper Mx10000 | ||
Juniper Mx10003 | ||
Juniper Mx10008 | ||
Juniper Mx10016 | ||
Juniper Mx104 | ||
Juniper Mx150 | ||
Juniper Mx2008 | ||
Juniper Mx2010 | ||
Juniper Mx2020 | ||
Juniper Mx204 | ||
Juniper Mx240 | ||
Juniper Mx40 | ||
Juniper Mx480 | ||
Juniper Mx5 | ||
Juniper Mx80 | ||
Juniper Mx960 | ||
Juniper Srx100 | ||
Juniper Srx110 | ||
Juniper Srx1400 | ||
Juniper Srx1500 | ||
Juniper Srx210 | ||
Juniper Srx220 | ||
Juniper Srx240 | ||
Juniper Srx240h2 | ||
Juniper Srx300 | ||
Juniper Srx320 | ||
Juniper Srx340 | ||
Juniper Srx3400 | ||
Juniper Srx345 | ||
Juniper Srx3600 | ||
Juniper Srx380 | ||
Juniper Srx4000 | ||
Juniper Srx4100 | ||
Juniper Srx4200 | ||
Juniper Srx4600 | ||
Juniper Srx5000 | ||
Juniper Srx5400 | ||
Juniper Srx550 | ||
Juniper Srx550 Hm | ||
Juniper Srx550m | ||
Juniper Srx5600 | ||
Juniper Srx5800 | ||
Juniper Srx650 |
The following software releases have been updated to resolve this specific issue: 18.2R3, 18.3R3, 18.4R2-S9, 18.4R3, 19.1R2, 19.2R1-S1, 19.2R2, 19.3R1, and all subsequent releases.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.