First published: Fri Apr 12 2024(Updated: )
An Improper Handling of Exceptional Conditions vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based, unauthenticated attacker to send a specific routing update, causing an rpd core due to memory corruption, leading to a Denial of Service (DoS). This issue can only be triggered when the system is configured for CoS-based forwarding (CBF) with a policy map containing a cos-next-hop-map action (see below). This issue affects: Junos OS: * all versions before 20.4R3-S10, * from 21.2 before 21.2R3-S8, * from 21.3 before 21.3R3, * from 21.4 before 21.4R3, * from 22.1 before 22.1R2; Junos OS Evolved: * all versions before 21.2R3-S8-EVO, * from 21.3 before 21.3R3-EVO, * from 21.4 before 21.4R3-EVO, * from 22.1 before 22.1R2-EVO.
Credit: sirt@juniper.net
Affected Software | Affected Version | How to fix |
---|---|---|
Juniper Networks Junos OS | <20.4R3-S10>=undefined>=undefined>=undefined>=undefined | |
Juniper Networks Junos OS Evolved | <21.2R3-S8-EVO>=undefined>=undefined>=undefined | |
Juniper JUNOS | <20.4 | |
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 | =20.4-r3 | |
Juniper JUNOS | =20.4-r3-s1 | |
Juniper JUNOS | =20.4-r3-s2 | |
Juniper JUNOS | =20.4-r3-s3 | |
Juniper JUNOS | =20.4-r3-s4 | |
Juniper JUNOS | =20.4-r3-s5 | |
Juniper JUNOS | =20.4-r3-s6 | |
Juniper JUNOS | =20.4-r3-s7 | |
Juniper JUNOS | =20.4-r3-s8 | |
Juniper JUNOS | =20.4-r3-s9 | |
Juniper JUNOS | =21.2 | |
Juniper JUNOS | =21.2-r1 | |
Juniper JUNOS | =21.2-r1-s1 | |
Juniper JUNOS | =21.2-r1-s2 | |
Juniper JUNOS | =21.2-r2 | |
Juniper JUNOS | =21.2-r2-s1 | |
Juniper JUNOS | =21.2-r2-s2 | |
Juniper JUNOS | =21.2-r3 | |
Juniper JUNOS | =21.2-r3-s1 | |
Juniper JUNOS | =21.2-r3-s2 | |
Juniper JUNOS | =21.2-r3-s3 | |
Juniper JUNOS | =21.2-r3-s4 | |
Juniper JUNOS | =21.2-r3-s5 | |
Juniper JUNOS | =21.2-r3-s6 | |
Juniper JUNOS | =21.2-r3-s7 | |
Juniper JUNOS | =21.3 | |
Juniper JUNOS | =21.3-r1 | |
Juniper JUNOS | =21.3-r1-s1 | |
Juniper JUNOS | =21.3-r1-s2 | |
Juniper JUNOS | =21.3-r2 | |
Juniper JUNOS | =21.3-r2-s1 | |
Juniper JUNOS | =21.3-r2-s2 | |
Juniper JUNOS | =21.4 | |
Juniper JUNOS | =21.4-r1 | |
Juniper JUNOS | =21.4-r1-s1 | |
Juniper JUNOS | =21.4-r1-s2 | |
Juniper JUNOS | =21.4-r2 | |
Juniper JUNOS | =21.4-r2-s1 | |
Juniper JUNOS | =21.4-r2-s2 | |
Juniper JUNOS | =22.1 | |
Juniper JUNOS | =22.1-r1 | |
Juniper JUNOS | =22.1-r1-s1 | |
Juniper JUNOS | =22.1-r1-s2 | |
Juniper Junos os Evolved | <21.2 | |
Juniper Junos os Evolved | =21.2 | |
Juniper Junos os Evolved | =21.2-r1 | |
Juniper Junos os Evolved | =21.2-r1-s1 | |
Juniper Junos os Evolved | =21.2-r1-s2 | |
Juniper Junos os Evolved | =21.2-r2 | |
Juniper Junos os Evolved | =21.2-r2-s1 | |
Juniper Junos os Evolved | =21.2-r2-s2 | |
Juniper Junos os Evolved | =21.2-r3 | |
Juniper Junos os Evolved | =21.2-r3-s1 | |
Juniper Junos os Evolved | =21.2-r3-s2 | |
Juniper Junos os Evolved | =21.2-r3-s3 | |
Juniper Junos os Evolved | =21.2-r3-s4 | |
Juniper Junos os Evolved | =21.2-r3-s5 | |
Juniper Junos os Evolved | =21.2-r3-s6 | |
Juniper Junos os Evolved | =21.2-r3-s7 | |
Juniper Junos os Evolved | =21.3 | |
Juniper Junos os Evolved | =21.3-r1 | |
Juniper Junos os Evolved | =21.3-r1-s1 | |
Juniper Junos os Evolved | =21.3-r2 | |
Juniper Junos os Evolved | =21.3-r2-s1 | |
Juniper Junos os Evolved | =21.3-r2-s2 | |
Juniper Junos os Evolved | =21.4 | |
Juniper Junos os Evolved | =21.4-r1 | |
Juniper Junos os Evolved | =21.4-r1-s1 | |
Juniper Junos os Evolved | =21.4-r1-s2 | |
Juniper Junos os Evolved | =21.4-r2 | |
Juniper Junos os Evolved | =21.4-r2-s1 | |
Juniper Junos os Evolved | =21.4-r2-s2 | |
Juniper Junos os Evolved | =22.1 | |
Juniper Junos os Evolved | =22.1-r1 | |
Juniper Junos os Evolved | =22.1-r1-s1 | |
Juniper Junos os Evolved | =22.1-r1-s2 |
The following software releases have been updated to resolve this specific issue: Junos OS: 20.4R3-S10, 21.3R3, 21.4R3, 22.1R2, 22.2R1, and all subsequent releases. Junos OS Evolved: 21.3R3-EVO, 21.4R3-EVO, 22.1R2-EVO, 22.2R1-EVO, and all subsequent releases.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-30382 has a high severity rating due to its potential to cause memory corruption and crash the routing protocol daemon.
To fix CVE-2024-30382, you should upgrade to the latest patched version of Junos OS or Junos OS Evolved as specified by Juniper Networks.
CVE-2024-30382 affects Junos OS versions up to 20.4R3-S10 and Junos OS Evolved up to 21.2R3-S8-EVO.
Yes, CVE-2024-30382 can be exploited remotely by an unauthenticated attacker via specific routing updates.
The potential impacts of CVE-2024-30382 include network disruptions and service outages due to the crashing of the routing protocol daemon.