First published: Thu Apr 22 2021(Updated: )
A vulnerability in the processing of traffic matching a firewall filter containing a syslog action in Juniper Networks Junos OS on MX Series with MPC10/MPC11 cards installed, PTX10003 and PTX10008 Series devices, will cause the line card to crash and restart, creating a Denial of Service (DoS). Continued receipt and processing of packets matching the firewall filter can create a sustained Denial of Service (DoS) condition. When traffic hits the firewall filter, configured on lo0 or any physical interface on the line card, containing a term with a syslog action (e.g. 'term <name> then syslog'), the affected line card will crash and restart, impacting traffic processing through the ports of the line card. This issue only affects MX Series routers with MPC10 or MPC11 line cards, and PTX10003 or PTX10008 Series packet transport routers. No other platforms or models of line cards are affected by this issue. Note: This issue has also been identified and described in technical service bulletin TSB17931 (login required). This issue affects: Juniper Networks Junos OS on MX Series: 19.3 versions prior to 19.3R3-S2; 19.4 versions prior to 19.4R3-S2; 20.1 versions prior to 20.1R3; 20.2 versions prior to 20.2R2-S2, 20.2R3; 20.3 versions prior to 20.3R3; 20.4 versions prior to 20.4R2. Juniper Networks Junos OS Evolved on PTX10003, PTX10008: All versions prior to 20.4R2-EVO. This issue does not affect Juniper Networks Junos OS versions prior to 19.3R1.
Credit: sirt@juniper.net
Affected Software | Affected Version | How to fix |
---|---|---|
Juniper JUNOS | =19.3 | |
Juniper JUNOS | =19.3-r1 | |
Juniper JUNOS | =19.3-r1-s1 | |
Juniper JUNOS | =19.3-r2 | |
Juniper JUNOS | =19.3-r2-s1 | |
Juniper JUNOS | =19.3-r2-s2 | |
Juniper JUNOS | =19.3-r2-s3 | |
Juniper JUNOS | =19.3-r2-s4 | |
Juniper JUNOS | =19.3-r2-s5 | |
Juniper JUNOS | =19.3-r3 | |
Juniper JUNOS | =19.4-r1 | |
Juniper JUNOS | =19.4-r1-s1 | |
Juniper JUNOS | =19.4-r1-s2 | |
Juniper JUNOS | =19.4-r2 | |
Juniper JUNOS | =19.4-r2-s1 | |
Juniper JUNOS | =19.4-r2-s2 | |
Juniper JUNOS | =19.4-r3 | |
Juniper JUNOS | =19.4-r3-s1 | |
Juniper JUNOS | =20.1-r1 | |
Juniper JUNOS | =20.1-r1-s1 | |
Juniper JUNOS | =20.1-r1-s2 | |
Juniper JUNOS | =20.1-r1-s3 | |
Juniper JUNOS | =20.1-r1-s4 | |
Juniper JUNOS | =20.1-r2 | |
Juniper JUNOS | =20.1-r2-s1 | |
Juniper JUNOS | =20.2-r1 | |
Juniper JUNOS | =20.2-r1-s1 | |
Juniper JUNOS | =20.2-r1-s2 | |
Juniper JUNOS | =20.2-r1-s3 | |
Juniper JUNOS | =20.2-r2 | |
Juniper JUNOS | =20.2-r2-s1 | |
Juniper JUNOS | =20.3-r1 | |
Juniper JUNOS | =20.3-r2 | |
Juniper JUNOS | =20.4-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 Junos Os Evolved | =18.3-r1 | |
Juniper Junos Os Evolved | =19.1-r1 | |
Juniper Junos Os Evolved | =19.1-r2 | |
Juniper Junos Os Evolved | =19.2-r1 | |
Juniper Junos Os Evolved | =19.2-r2 | |
Juniper Junos Os Evolved | =19.3-r1 | |
Juniper Junos Os Evolved | =19.3-r2 | |
Juniper Junos Os Evolved | =20.1-r1 | |
Juniper Junos Os Evolved | =20.1-r2 | |
Juniper Junos Os Evolved | =20.2-r1 | |
Juniper Junos Os Evolved | =20.2-r2 | |
Juniper Junos Os Evolved | =20.3-r1 | |
Juniper Junos Os Evolved | =20.3-r2 | |
Juniper Junos Os Evolved | =20.4-r1 | |
Juniper Ptx10003 | ||
Juniper Ptx10008 |
The following software releases have been updated to resolve this specific issue: Junos OS 19.4R3-S2, 20.1R3, 20.2R2-S2, 20.2R3, 20.3R3, 20.4R2, 21.1R1, and all subsequent releases. Junos OS Evolved 20.4R2-EVO, 21.1R1-EVO, and all subsequent releases.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.