CVE-2024-39559

Junos OS Evolved: Receipt of a specific TCP packet may result in a system crash (vmcore) on dual RE systems with NSR enabled

MEDIUM
5.9
CVSS Score
Published: July 10, 2024 at 10:42 PM UTC
Updated: June 17, 2026 at 07:42 AM UTC
2 products affected across 2 vendorsJunos OS EvolvedJunos OS Evolved

Using Junos OS Evolved by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS Evolved - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.9
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 21.2R3-S8-EVO21.4-EVO ≤ v < 21.4R3-S6-EVO22.1-EVO ≤ v < 22.1R3-S4-EVO22.2-EVO ≤ v < 22.2R3-S4-EVO22.3-EVO ≤ v < 22.3R3-S3-EVO22.4-EVO ≤ v < 22.4R2-S2-EVO, 22.4R3-EVO21.4-EVO22.1-EVO22.2-EVO22.3-EVO22.4-EVO
Affected range stops below 21.2R3-S8-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R3-S6-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R3-S4-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S4-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R3-S3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R2-S2-EVO, 22.4R3-EVO, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.9MEDIUMjuniper
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-754

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card