CVE-2024-47502

Junos OS Evolved: TCP session state is not always cleared on the Routing Engine leading to DoS

HIGH
7.5
CVSS Score
Published: October 11, 2024 at 03:31 PM UTC
Updated: June 17, 2026 at 07:57 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
HIGH7.5
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

An Allocation of Resources Without Limits or Throttling vulnerability in the kernel of Juniper Networks Junos OS Evolved allows an unauthenticated, network based attacker to cause a Denial of Service (DoS). In specific cases the state of TCP sessions that are terminated is not cleared, which over time leads to an exhaustion of resources, preventing new connections to the control plane from being established. A continuously increasing number of connections shown by: user@host > show system connections is indicative of the problem. To recover the respective RE needs to be restarted manually. This issue only affects IPv4 but does not affect IPv6. This issue only affects TCP sessions established in-band (over an interface on an FPC) but not out-of-band (over the management ethernet port on the routing-engine). This issue affects Junos OS Evolved: * All versions before 21.4R3-S9-EVO, * 22.2 versions before 22.2R3-S4-EVO, * 22.4 version before 22.4R3-S3-EVO, * 23.2 versions before 23.2R2-S1-EVO, * 23.4 versions before 23.4R2-EVO.

Affected

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

Affected range stops below 21.4r3-s9-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.4r3-s3-evo, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2r2-s1-evo, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.4r2-evo, so it looks safe — our inference, not a vendor statement
v < 21.4R3-S9-EVO22.2 ≤ v < 22.2R3-S4-EVO22.4 ≤ v < 22.4R3-S3-EVO23.2 ≤ v < 23.2R2-S1-EVO23.4 ≤ v < 23.4R2-EVO22.222.423.223.4
Affected range stops below 21.4R3-S9-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.4R3-S3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R2-S1-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.4R2-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 exploitAutomatablePartial impact

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

CVSS

7.5HIGHjuniper
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-770

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