First published: Wed Jul 10 2024(Updated: )
An Improper Check for Unusual or Exceptional Conditions vulnerability in packet processing of Juniper Networks Junos OS Evolved may allow a network-based unauthenticated attacker to crash the device (vmcore) by sending a specific TCP packet over an established TCP session with MD5 authentication enabled, destined to an accessible port on the device, resulting in a Denial of Service (DoS). The receipt of this packet must occur within a specific timing window outside the attacker's control (i.e., race condition). Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition. This issue only affects dual RE systems with Nonstop Active Routing (NSR) enabled. Exploitation can only occur over TCP sessions with MD5 authentication enabled (e.g., BGP with MD5 authentication). This issue affects Junos OS Evolved: * All versions before 21.2R3-S8-EVO, * from 21.4-EVO before 21.4R3-S6-EVO, * from 22.1-EVO before 22.1R3-S4-EVO, * from 22.2-EVO before 22.2R3-S4-EVO, * from 22.3-EVO before 22.3R3-S3-EVO, * from 22.4-EVO before 22.4R2-S2-EVO, 22.4R3-EVO.
Credit: sirt@juniper.net
Affected Software | Affected Version | How to fix |
---|---|---|
Juniper Networks Junos OS | <21.2R3-S8-EVO>=21.4-EVO<21.4R3-S6-EVO>=22.1-EVO<22.1R3-S4-EVO>=22.2-EVO<22.2R3-S4-EVO>=22.3-EVO<22.3R3-S3-EVO>=22.4-EVO<22.4R2-S2-EVO | |
Juniper JUNOS | <21.2 | |
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.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 | =21.4-r3 | |
Juniper JUNOS | =21.4-r3-s1 | |
Juniper JUNOS | =21.4-r3-s2 | |
Juniper JUNOS | =21.4-r3-s3 | |
Juniper JUNOS | =21.4-r3-s4 | |
Juniper JUNOS | =21.4-r3-s5 | |
Juniper JUNOS | =22.1 | |
Juniper JUNOS | =22.1-r1 | |
Juniper JUNOS | =22.1-r1-s1 | |
Juniper JUNOS | =22.1-r1-s2 | |
Juniper JUNOS | =22.1-r2 | |
Juniper JUNOS | =22.1-r2-s1 | |
Juniper JUNOS | =22.1-r3 | |
Juniper JUNOS | =22.1-r3-s1 | |
Juniper JUNOS | =22.1-r3-s2 | |
Juniper JUNOS | =22.1-r3-s3 | |
Juniper JUNOS | =22.2 | |
Juniper JUNOS | =22.2-r1 | |
Juniper JUNOS | =22.2-r1-s1 | |
Juniper JUNOS | =22.2-r1-s2 | |
Juniper JUNOS | =22.2-r2 | |
Juniper JUNOS | =22.2-r2-s1 | |
Juniper JUNOS | =22.2-r2-s2 | |
Juniper JUNOS | =22.2-r3 | |
Juniper JUNOS | =22.2-r3-s1 | |
Juniper JUNOS | =22.2-r3-s2 | |
Juniper JUNOS | =22.2-r3-s3 | |
Juniper JUNOS | =22.3 | |
Juniper JUNOS | =22.3-r1 | |
Juniper JUNOS | =22.3-r1-s1 | |
Juniper JUNOS | =22.3-r1-s2 | |
Juniper JUNOS | =22.3-r2 | |
Juniper JUNOS | =22.3-r2-s1 | |
Juniper JUNOS | =22.3-r2-s2 | |
Juniper JUNOS | =22.3-r3 | |
Juniper JUNOS | =22.3-r3-s1 | |
Juniper JUNOS | =22.3-r3-s2 | |
Juniper JUNOS | =22.4 | |
Juniper JUNOS | =22.4-r1 | |
Juniper JUNOS | =22.4-r1-s1 | |
Juniper JUNOS | =22.4-r1-s2 | |
Juniper JUNOS | =22.4-r2 | |
Juniper JUNOS | =22.4-r2-s1 |
The following software releases have been updated to resolve this specific issue: 21.2R3-S8-EVO, 21.4R3-S6-EVO, 22.1R3-S4-EVO, 22.2R3-S4-EVO, 22.3R3-S3-EVO, 22.4R2-S2-EVO, 22.4R3-EVO, 23.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-39559 is considered a critical vulnerability due to its potential to crash affected devices via unauthorized network access.
To fix CVE-2024-39559, update your Junos OS Evolved to the latest available version that addresses this vulnerability.
CVE-2024-39559 affects multiple versions of Juniper Networks Junos OS Evolved, primarily versions prior to 21.2R3-S8-EVO.
Yes, CVE-2024-39559 can be exploited by an unauthenticated attacker remotely through specific TCP packets.
If your system is vulnerable to CVE-2024-39559, it may experience a crash or failure, leading to potential downtime and service disruptions.