medium
5.9
CWE
367 362
Advisory Published
Updated

CVE-2022-22220: Junos OS and Junos OS Evolved: Due to a race condition the rpd process can crash upon receipt of a BGP update message containing flow spec route

First published: Wed Oct 12 2022(Updated: )

A Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in Routing Protocol Daemon (rpd) of Juniper Networks Junos OS, Junos OS Evolved allows a network-based unauthenticated attacker to cause a Denial of Service (DoS). When a BGP flow route with redirect IP extended community is received, and the reachability to the next-hop of the corresponding redirect IP is flapping, the rpd process might crash. Whether the crash occurs depends on the timing of the internally processing of these two events and is outside the attackers control. Please note that this issue also affects Route-Reflectors unless 'routing-options flow firewall-install-disable' is configured. This issue affects: Juniper Networks Junos OS: 18.4 versions prior to 18.4R2-S10, 18.4R3-S10; 19.1 versions prior to 19.1R3-S7; 19.2 versions prior to 19.2R1-S8, 19.2R3-S4; 19.4 versions prior to 19.4R3-S8; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S2; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2. Juniper Networks Junos OS Evolved: All versions prior to 20.4R2-EVO; 21.1-EVO versions prior to 21.1R2-EVO. This issue does not affect Juniper Networks Junos OS versions prior to 18.4R1.

Credit: sirt@juniper.net

Affected SoftwareAffected VersionHow to fix
Juniper Junos<18.4
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=18.4-r2-s9
Juniper Junos=18.4-r3-s10
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.1-r2
Juniper Junos=19.1-r2-s1
Juniper Junos=19.1-r2-s2
Juniper Junos=19.1-r2-s3
Juniper Junos=19.1-r3
Juniper Junos=19.1-r3-s1
Juniper Junos=19.1-r3-s2
Juniper Junos=19.1-r3-s3
Juniper Junos=19.1-r3-s4
Juniper Junos=19.1-r3-s5
Juniper Junos=19.1-r3-s6
Juniper Junos=19.4
Juniper Junos=19.4-r1
Juniper Junos=19.4-r1-s1
Juniper Junos=19.4-r1-s2
Juniper Junos=19.4-r1-s3
Juniper Junos=19.4-r1-s4
Juniper Junos=19.4-r2
Juniper Junos=19.4-r2-s1
Juniper Junos=19.4-r2-s2
Juniper Junos=19.4-r2-s3
Juniper Junos=19.4-r2-s4
Juniper Junos=19.4-r2-s5
Juniper Junos=19.4-r3-s6
Juniper Junos=19.4-r3-s7
Juniper Junos=20.2
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.2-r2-s2
Juniper Junos=20.2-r2-s3
Juniper Junos=20.2-r3
Juniper Junos=20.2-r3-s1
Juniper Junos=20.2-r3-s2
Juniper Junos=20.3
Juniper Junos=20.3-r1
Juniper Junos=20.3-r1-s1
Juniper Junos=20.3-r1-s2
Juniper Junos=20.3-r2
Juniper Junos=20.3-r2-s1
Juniper Junos=20.3-r3
Juniper Junos=20.3-r3-s1
Juniper Junos=20.3-r3-s2
Juniper Junos=20.4
Juniper Junos=20.4-r1
Juniper Junos=20.4-r1-s1
Juniper Junos=20.4-r2
Juniper Junos=20.4-r2-s1
Juniper Junos=20.4-r2-s2
Juniper Junos=21.1
Juniper Junos=21.1-r1
Juniper Junos=21.1-r1-s1
Juniper Networks Junos OS<20.4
Juniper Networks Junos OS=20.4
Juniper Networks Junos OS=20.4-r1
Juniper Networks Junos OS=20.4-r1-s1
Juniper Networks Junos OS=20.4-r1-s2
Juniper Networks Junos OS=21.1
Juniper Networks Junos OS=21.1-r1
Juniper Networks Junos OS=21.1-r1-s1

Remedy

The following software releases have been updated to resolve this specific issue: Junos OS: 18.4R2-S10, 18.4R3-S10, 19.1R3-S7, 19.2R1-S8, 19.2R3-S4, 19.4R3-S8, 20.2R3-S3, 20.3R3-S2, 20.4R3, 21.1R2, 21.2R1, and all subsequent releases. Junos OS Evolved: 20.4R2-EVO, 21.1R2-EVO, 21.2R1-EVO, and all subsequent releases.

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

Frequently Asked Questions

  • What is the severity of CVE-2022-22220?

    CVE-2022-22220 has been classified as a high severity vulnerability due to its potential to enable a Denial of Service (DoS) attack.

  • How do I fix CVE-2022-22220?

    To remediate CVE-2022-22220, update the Junos OS software to the latest version that is not affected by this vulnerability.

  • Which versions of Junos OS are affected by CVE-2022-22220?

    CVE-2022-22220 affects Junos OS versions up to 18.4 and includes several 19.x and 20.x versions as well.

  • Can CVE-2022-22220 be exploited remotely?

    Yes, an unauthenticated network-based attacker can exploit CVE-2022-22220 to cause a Denial of Service.

  • What type of vulnerability is CVE-2022-22220 categorized as?

    CVE-2022-22220 is categorized as a Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203