First published: Fri Oct 16 2020(Updated: )
On Juniper Networks EX4300-MP Series, EX4600 Series and QFX5K Series deployed in a Virtual Chassis configuration, receipt of a stream of specific layer 2 frames can cause high CPU load, which could lead to traffic interruption. This issue does not occur when the device is deployed in Stand Alone configuration. The offending layer 2 frame packets can originate only from within the broadcast domain where the device is connected. This issue affects Juniper Networks Junos OS on EX4300-MP Series, EX4600 Series and QFX5K Series: 17.3 versions prior to 17.3R3-S9; 17.4 versions prior to 17.4R2-S11, 17.4R3-S2, 17.4R3-S3; 18.1 versions prior to 18.1R3-S11; 18.2 versions prior to 18.2R3-S5; 18.3 versions prior to 18.3R2-S4, 18.3R3-S3; 18.4 versions prior to 18.4R2-S5, 18.4R3-S4; 19.1 versions prior to 19.1R3-S2; 19.2 versions prior to 19.2R1-S5, 19.2R3; 19.3 versions prior to 19.3R2-S4, 19.3R3; 19.4 versions prior to 19.4R1-S3, 19.4R2-S1, 19.4R3; 20.1 versions prior to 20.1R1-S3, 20.1R2.
Credit: sirt@juniper.net
Affected Software | Affected Version | How to fix |
---|---|---|
Juniper Junos | =17.3 | |
Juniper Junos | =17.3-r1-s1 | |
Juniper Junos | =17.3-r2 | |
Juniper Junos | =17.3-r2-s1 | |
Juniper Junos | =17.3-r2-s2 | |
Juniper Junos | =17.3-r2-s3 | |
Juniper Junos | =17.3-r2-s4 | |
Juniper Junos | =17.3-r2-s5 | |
Juniper Junos | =17.3-r3 | |
Juniper Junos | =17.3-r3-s1 | |
Juniper Junos | =17.3-r3-s2 | |
Juniper Junos | =17.3-r3-s3 | |
Juniper Junos | =17.3-r3-s4 | |
Juniper Junos | =17.3-r3-s7 | |
Juniper Junos | =17.3-r3-s8 | |
Juniper Junos | =17.4 | |
Juniper Junos | =17.4-r1 | |
Juniper Junos | =17.4-r1-s1 | |
Juniper Junos | =17.4-r1-s2 | |
Juniper Junos | =17.4-r1-s4 | |
Juniper Junos | =17.4-r1-s5 | |
Juniper Junos | =17.4-r1-s6 | |
Juniper Junos | =17.4-r1-s7 | |
Juniper Junos | =17.4-r2 | |
Juniper Junos | =17.4-r2-s1 | |
Juniper Junos | =17.4-r2-s10 | |
Juniper Junos | =17.4-r2-s2 | |
Juniper Junos | =17.4-r2-s3 | |
Juniper Junos | =17.4-r2-s4 | |
Juniper Junos | =17.4-r2-s5 | |
Juniper Junos | =17.4-r2-s6 | |
Juniper Junos | =17.4-r2-s7 | |
Juniper Junos | =17.4-r2-s8 | |
Juniper Junos | =17.4-r2-s9 | |
Juniper Junos | =17.4-r3 | |
Juniper Junos | =17.4-r3-s1 | |
Juniper Junos | =17.4-r3-s2 | |
Juniper Junos | =18.1 | |
Juniper Junos | =18.1-r1 | |
Juniper Junos | =18.1-r2 | |
Juniper Junos | =18.1-r2-s1 | |
Juniper Junos | =18.1-r2-s2 | |
Juniper Junos | =18.1-r2-s4 | |
Juniper Junos | =18.1-r3 | |
Juniper Junos | =18.1-r3-s1 | |
Juniper Junos | =18.1-r3-s10 | |
Juniper Junos | =18.1-r3-s2 | |
Juniper Junos | =18.1-r3-s3 | |
Juniper Junos | =18.1-r3-s4 | |
Juniper Junos | =18.1-r3-s6 | |
Juniper Junos | =18.1-r3-s7 | |
Juniper Junos | =18.1-r3-s8 | |
Juniper Junos | =18.1-r3-s9 | |
Juniper Junos | =18.2 | |
Juniper Junos | =18.2-r1 | |
Juniper Junos | =18.2-r1 | |
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-r3 | |
Juniper Junos | =18.2-r3-s1 | |
Juniper Junos | =18.2-r3-s2 | |
Juniper Junos | =18.2-r3-s3 | |
Juniper Junos | =18.2-r3-s4 | |
Juniper Junos | =18.3 | |
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-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-r3 | |
Juniper Junos | =18.3-r3-s1 | |
Juniper Junos | =18.3-r3-s2 | |
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-s5 | |
Juniper Junos | =18.4-r1-s6 | |
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-r3 | |
Juniper Junos | =18.4-r3-s1 | |
Juniper Junos | =18.4-r3-s2 | |
Juniper Junos | =18.4-r3-s3 | |
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-r2 | |
Juniper Junos | =19.1-r2-s1 | |
Juniper Junos | =19.1-r3 | |
Juniper Junos | =19.1-r3-s1 | |
Juniper Junos | =19.2 | |
Juniper Junos | =19.2-r1 | |
Juniper Junos | =19.2-r1-s1 | |
Juniper Junos | =19.2-r1-s2 | |
Juniper Junos | =19.2-r1-s3 | |
Juniper Junos | =19.2-r1-s4 | |
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.4-r1 | |
Juniper Junos | =19.4-r1-s1 | |
Juniper Junos | =19.4-r1-s2 | |
Juniper Junos | =19.4-r2 | |
Juniper Junos | =20.1-r1 | |
Juniper Junos | =20.1-r1-s1 | |
Juniper Junos | =20.1-r1-s2 | |
Juniper EX4300 | ||
Juniper QFX5100 | ||
Juniper QFX5120 | ||
Juniper QFX5130 | ||
Juniper QFX5200-48Y |
The following software releases have been updated to resolve this specific issue: Junos OS 17.3R3-S9, 17.4R2-S11, 17.4R3-S2, 17.4R3-S3, 18.1R3-S11, 18.2R3-S5, 18.3R2-S4, 18.3R3-S3, 18.4R2-S5, 18.4R3-S4, 19.1R3-S2, 19.2R1-S5, 19.2R3, 19.3R2-S4, 19.3R3, 19.4R1-S3, 19.4R2-S1, 19.4R3, 20.1R1-S3, 20.1R2, 20.2R1, and all subsequent releases.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-1689 has a severity level of medium, indicating that it can cause significant disruption to network traffic.
To mitigate CVE-2020-1689, Juniper Networks recommends upgrading to the latest versions of JUNOS software that address this vulnerability.
CVE-2020-1689 affects Juniper Networks EX4300-MP Series, EX4600 Series, and QFX5K Series deployed in a Virtual Chassis configuration.
The impact of CVE-2020-1689 is high CPU load on the affected devices, which can lead to traffic interruption.
Currently, the best practice is to apply the recommended software updates from Juniper Networks, as there are no documented workarounds.