high
7.5
CWE
20 1173
Advisory Published
Updated

CVE-2020-1640: Junos OS: Receipt of certain genuine BGP packets from any BGP Speaker causes RPD to crash.

First published: Fri Jul 17 2020(Updated: )

An improper use of a validation framework when processing incoming genuine BGP packets within Juniper Networks RPD (routing protocols process) daemon allows an attacker to crash RPD thereby causing a Denial of Service (DoS) condition. This framework requires these packets to be passed. By continuously sending any of these types of formatted genuine packets, an attacker can repeatedly crash the RPD process causing a sustained Denial of Service. Authentication to the BGP peer is not required. This issue can be initiated or propagated through eBGP and iBGP and can impact devices in either modes of use as long as the devices are configured to support the compromised framework and a BGP path is activated or active. This issue affects: Juniper Networks Junos OS 16.1 versions 16.1R7-S6 and later versions prior to 16.1R7-S8; 17.3 versions 17.3R2-S5, 17.3R3-S6 and later versions prior to 17.3R3-S8; 17.4 versions 17.4R2-S7, 17.4R3 and later versions prior to 17.4R2-S11, 17.4R3-S2; 18.1 versions 18.1R3-S7 and later versions prior to 18.1R3-S10; 18.2 versions 18.2R2-S6, 18.2R3-S2 and later versions prior to 18.2R2-S7, 18.2R3-S5; 18.2X75 versions 18.2X75-D12, 18.2X75-D32, 18.2X75-D33, 18.2X75-D51, 18.2X75-D60, 18.2X75-D411, 18.2X75-D420 and later versions prior to 18.2X75-D32, 18.2X75-D33, 18.2X75-D420, 18.2X75-D52, 18.2X75-D60, 18.2X75-D65, 18.2X75-D70;(*1) 18.3 versions 18.3R1-S6, 18.3R2-S3, 18.3R3 and later versions prior to 18.3R2-S4, 18.3R3-S2; 18.4 versions 18.4R1-S5, 18.4R2-S4, 18.4R3 and later versions prior to 18.4R1-S7, 18.4R2-S5, 18.4R3-S3(*2); 19.1 versions 19.1R1-S3, 19.1R2 and later versions prior to 19.1R1-S5, 19.1R2-S2, 19.1R3-S2; 19.2 versions 19.2R1-S2, 19.2R2 and later versions prior to 19.2R1-S5, 19.2R2, 19.2R3; 19.3 versions prior to 19.3R2-S3, 19.3R3; 19.4 versions prior to 19.4R1-S2, 19.4R2, 19.4R3; 20.1 versions prior to 20.1R1-S1, 20.1R2. This issue does not affect Junos OS prior to 16.1R1. This issue affects IPv4 and IPv6 traffic.

Credit: sirt@juniper.net

Affected SoftwareAffected VersionHow to fix
Juniper JUNOS=16.1-r7-s6
Juniper JUNOS=16.1-r7-s7
Juniper JUNOS=17.3-r2-s5
Juniper JUNOS=17.3-r3-s6
Juniper JUNOS=17.3-r3-s7
Juniper JUNOS=17.4-r2-s10
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=18.1-r3-s7
Juniper JUNOS=18.1-r3-s8
Juniper JUNOS=18.1-r3-s9
Juniper JUNOS=18.2-r2-s6
Juniper JUNOS=18.2-r3-s2
Juniper JUNOS=18.2-r3-s3
Juniper JUNOS=18.2-r3-s4
Juniper JUNOS=18.2x75-d12
Juniper JUNOS=18.2x75-d411
Juniper JUNOS=18.2x75-d51
Juniper JUNOS=18.3-r1-s6
Juniper JUNOS=18.3-r2-s3
Juniper JUNOS=18.3-r3
Juniper JUNOS=18.3-r3-s1
Juniper JUNOS=18.4-r1-s5
Juniper JUNOS=18.4-r1-s6
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=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-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.4-r1
Juniper JUNOS=19.4-r1-s1
Juniper JUNOS=20.1-r1

Remedy

The following software releases have been updated to resolve this specific issue: 16.1R7-S8, 17.3R3-S8, 17.4R2-S11, 17.4R3-S2, 18.1R3-S10, 18.2R2-S7, 18.2R3-S5, 18.2X75-D32, 18.2X75-D33, 18.2X75-D420, 18.2X75-D52, 18.2X75-D60, 18.2X75-D65, 18.2X75-D70;(*1), 18.3R2-S4, 18.3R3-S2, 18.4R1-S7, 18.4R2-S5, 18.4R3-S3(*2), 19.1R1-S5, 19.1R2-S2, 19.1R3-S2, 19.2R1-S5, 19.2R2, 19.2R3, 19.3R2-S3, 19.3R3, 19.4R1-S2, 19.4R2, 19.4R3, 20.1R1-S1, 20.1R2, 20.2R1, and subsequent releases. *1: For 18.2X75 customers. Please speak with your account manager regarding applicable respin release identifiers for affected-to to affected-from, and resolved-in release targets. *2: Pending publication.

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203