7.5
CWE
20
Advisory Published
Updated

CVE-2023-4481: Junos OS and Junos OS Evolved: A crafted BGP UPDATE message allows a remote attacker to de-peer (reset) BGP sessions (CVE-2023-4481)

First published: Thu Aug 31 2023(Updated: )

An Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). When certain specific crafted BGP UPDATE messages are received over an established BGP session, one BGP session may be torn down with an UPDATE message error, or the issue may propagate beyond the local system which will remain non-impacted, but may affect one or more remote systems. This issue is exploitable remotely as the crafted UPDATE message can propagate through unaffected systems and intermediate BGP speakers. Continuous receipt of the crafted BGP UPDATE messages will create a sustained Denial of Service (DoS) condition for impacted devices. This issue affects eBGP and iBGP, in both IPv4 and IPv6 implementations. This issue requires a remote attacker to have at least one established BGP session.

Credit: sirt@juniper.net sirt@juniper.net

Affected SoftwareAffected VersionHow to fix
Juniper JUNOS<=23.4
Juniper Junos Os Evolved<=23.4
<20.4
=20.4
=20.4-r1
=20.4-r1-s1
=20.4-r2
=20.4-r2-s1
=20.4-r2-s2
=20.4-r3
=20.4-r3-s1
=20.4-r3-s2
=20.4-r3-s3
=20.4-r3-s4
=20.4-r3-s5
=20.4-r3-s6
=20.4-r3-s7
=20.4-r3-s8
=20.4-r3-s9
=21.1
=21.1-r1
=21.1-r1-s1
=21.2
=21.2-r1
=21.2-r1-s1
=21.2-r1-s2
=21.2-r2
=21.2-r2-s1
=21.2-r2-s2
=21.2-r3
=21.2-r3-s1
=21.2-r3-s2
=21.2-r3-s3
=21.2-r3-s4
=21.3
=21.3-r1
=21.3-r1-s1
=21.3-r1-s2
=21.3-r2
=21.3-r2-s1
=21.3-r2-s2
=21.3-r3
=21.3-r3-s1
=21.3-r3-s2
=21.3-r3-s3
=21.3-r3-s4
=21.4
=21.4-r1
=21.4-r1-s1
=21.4-r1-s2
=21.4-r2
=21.4-r2-s1
=21.4-r2-s2
=21.4-r3
=21.4-r3-s1
=21.4-r3-s2
=21.4-r3-s3
=21.4-r3-s4
=22.1
=22.1-r1
=22.1-r1-s1
=22.1-r1-s2
=22.1-r2
=22.1-r2-s1
=22.1-r2-s2
=22.1-r3
=22.1-r3-s1
=22.1-r3-s2
=22.1-r3-s3
=22.2
=22.2-r1
=22.2-r1-s1
=22.2-r1-s2
=22.2-r2
=22.2-r2-s1
=22.2-r2-s2
=22.2-r3
=22.2-r3-s1
=22.2-r3-s2
=22.3
=22.3-r1
=22.3-r1-s1
=22.3-r1-s2
=22.3-r2
=22.3-r2-s1
=22.3-r2-s2
=22.3-r3
=22.4
=22.4-r1
=22.4-r1-s1
=22.4-r1-s2
=22.4-r2
=22.4-r2-s1
=22.4-r2-s2
=23.2
=23.2-r1
=23.2-r1-s1
=23.2-r1-s2
<20.4
=20.4
=20.4-r1
=20.4-r1-s1
=20.4-r1-s2
=20.4-r2
=20.4-r2-s1
=20.4-r2-s2
=20.4-r2-s3
=20.4-r3
=20.4-r3-s1
=20.4-r3-s2
=20.4-r3-s3
=20.4-r3-s4
=20.4-r3-s5
=20.4-r3-s6
=20.4-r3-s7
=20.4-r3-s8
=20.4-r3-s9
=21.2
=21.2-r1
=21.2-r1-s1
=21.2-r1-s2
=21.2-r2
=21.2-r2-s1
=21.2-r2-s2
=21.2-r3
=21.2-r3-s1
=21.2-r3-s2
=21.2-r3-s3
=21.2-r3-s4
=21.2-r3-s5
=21.2-r3-s6
=21.3
=21.3-r1
=21.3-r1-s1
=21.3-r2
=21.3-r2-s1
=21.3-r2-s2
=21.3-r3
=21.3-r3-s1
=21.3-r3-s2
=21.3-r3-s3
=21.3-r3-s4
=21.4
=21.4-r1
=21.4-r1-s1
=21.4-r1-s2
=21.4-r2
=21.4-r2-s1
=21.4-r2-s2
=21.4-r3
=21.4-r3-s1
=21.4-r3-s2
=21.4-r3-s3
=21.4-r3-s4
=22.1
=22.1-r1
=22.1-r1-s1
=22.1-r1-s2
=22.1-r2
=22.1-r2-s1
=22.1-r3
=22.1-r3-s1
=22.1-r3-s2
=22.1-r3-s3
=22.2
=22.2-r1
=22.2-r1-s1
=22.2-r1-s2
=22.2-r2
=22.2-r2-s1
=22.2-r2-s2
=22.2-r3
=22.2-r3-s1
=22.2-r3-s2
=22.3
=22.3-r1
=22.3-r1-s1
=22.3-r1-s2
=22.3-r2
=22.3-r2-s1
=22.3-r2-s2
=22.3-r3
=22.4
=22.4-r1
=22.4-r1-s1
=22.4-r1-s2
=22.4-r2
=22.4-r2-s1
=22.4-r2-s2
=22.4-r3
=23.2
=23.2-r1
=23.2-r1-s1
=23.2-r1-s2

Remedy

The following software releases have been updated to resolve this specific issue: Junos OS: 20.4R3-S10, 21.2R3-S7, 21.3R3-S5, 21.4R3-S5 or 21.4R3-S7, 22.1R3-S4, 22.2R3-S3, 22.3R3-S1, 22.4R3, 23.2R2, 23.3R2, 23.4R1, and all subsequent releases Note: except for Junos OS 21.4R3-S6 which is affected and unfixed. Junos OS Evolved: 20.4R3-S10-EVO, 21.2R3-S7-EVO, 21.3R3-S5-EVO, 21.4R3-S5-EVO, 22.1R3-S4-EVO, 22.2R3-S3-EVO, 22.3R3-S1-EVO, 22.4R3-EVO, 23.2R2-EVO, 23.4R1-EVO, and all subsequent releases. It is important that customers implement the workaround in addition to taking any updated software as these crafted UPDATE messages may be propagated to other devices even if non-impacted locally, thereby protecting the network by stopping the propagation of these crafted UPDATE messages. The workaround is to configure BGP error tolerance by way of:   [ protocols bgp bgp-error-tolerance ... ] Additional details can be found at https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/topic-map/bgp-error-messages.h... https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/topic-map/bgp-error-messages.html Juniper considers configuring this option to be a Best Common Practice (BCP) as it not only prevents this issue from happening, but protects against similar issues as well. This issue is being tracked as PR 1709837 https://prsearch.juniper.net/problemreport/PR1709837  which is visible on the Customer Support website. Note: Juniper SIRT's policy https://kb.juniper.net/KB16765  is not to evaluate releases which are beyond End of Engineering (EOE) or End of Life (EOL).

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.

Frequently Asked Questions

  • What is CVE-2023-4481?

    CVE-2023-4481 is an Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved.

  • What is the severity of CVE-2023-4481?

    CVE-2023-4481 has a severity rating of 7.5 out of 10, which is considered high.

  • How can an unauthenticated attacker exploit CVE-2023-4481?

    An unauthenticated attacker can exploit CVE-2023-4481 by sending certain specific crafted BGP UPDATE messages over the network.

  • What is the impact of CVE-2023-4481?

    The impact of CVE-2023-4481 is a Denial of Service (DoS) attack.

  • How can I mitigate CVE-2023-4481?

    To mitigate CVE-2023-4481, it is recommended to apply the necessary patches or upgrades provided by Juniper Networks.

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