CVE-2022-22240

Junos OS and Junos OS Evolved: An rpd memory leak might be observed while running a specific cli command in a RIB sharding scenario

MEDIUM
5.5
CVSS Score
Published: October 18, 2022 at 02:46 AM UTC
Updated: June 17, 2026 at 04:28 AM UTC
3 products affected across 2 vendorsJunosJunos OS EvolvedJunos OS Evolved

Using Junos OS by Juniper Networks?

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

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

Description

An Allocation of Resources Without Limits or Throttling and a Missing Release of Memory after Effective Lifetime vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a locally authenticated low privileged attacker to cause a Denial of Sevice (DoS). In a high-scaled BGP routing environment with rib-sharding enabled, two issues may occur when executing a specific CLI command. One is a memory leak issue with rpd where the leak rate is not constant, and the other is a temporary spike in rpd memory usage during command execution. This issue affects: Juniper Networks Junos OS 19.4 versions prior to 19.4R3-S9; 20.2 versions prior to 20.2R3-S5; 20.3 versions prior to 20.3R3-S2; 20.4 versions prior to 20.4R3-S1; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R1-S2, 21.2R2-S1, 21.2R3; 21.3 versions prior to 21.3R2. Juniper Networks Junos OS Evolved All versions prior to 20.4R3-S1-EVO; 21.1-EVO version 21.1R1-EVO and later versions; 21.2-EVO versions prior to 21.2R1-S2-EVO, 21.2R3-EVO; 21.3-EVO versions prior to 21.3R2-EVO. This issue does not affect Juniper Networks Junos OS versions prior to 19.2R1.

Affected

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

Vendor states this is fixed in 19.2R1 (unaffected)
Affected range stops below 19.4R3-S9, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.2R3-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.3R3-S2, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.4R3-S1, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.1R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2R1-S2, 21.2R2-S1, 21.2R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.3R2, so it looks safe — our inference, not a vendor statement
v < 20.4R3-S1-EVO21.1R1-EVO ≤ v < 21.1-EVO*21.2-EVO ≤ v < 21.2R1-S2-EVO, 21.2R3-EVO21.3-EVO ≤ v < 21.3R2-EVO21.1R1-EVO21.2-EVO21.3-EVO
Affected range stops below 20.4R3-S1-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.1-EVO*, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2R1-S2-EVO, 21.2R3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.3R2-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

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

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

CVSS

5.5MEDIUMjuniper
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-401CWE-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