CVE-2022-22225

Junos OS and Junos OS Evolved: In a BGP multipath scenario, when one of the contributing routes is flapping often and rapidly, rpd may crash

MEDIUM
5.9
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.9
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

A Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated attacker with an established BGP session to cause a Denial of Service (DoS). In a BGP multipath scenario, when one of the contributing routes is flapping often and rapidly, rpd may crash. As this crash depends on whether a route is a contributing route, and on the internal timing of the events triggered by the flap this vulnerability is outside the direct control of a potential attacker. This issue affects: Juniper Networks Junos OS 19.2 versions prior to 19.2R3-S6; 20.2 versions prior to 20.2R3-S4; 20.3 versions prior to 20.3R3-S3; 20.4 versions prior to 20.4R3-S4; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R2; 21.3 versions prior to 21.3R2. Juniper Networks Junos OS Evolved All versions prior to 20.4R3-S4-EVO; 21.1-EVO version 21.1R1-EVO and later versions; 21.2-EVO versions prior to 21.2R2-EVO; 21.3-EVO versions prior to 21.3R2-EVO. This issue does not affect: Juniper Networks Junos OS versions 19.2 versions prior to 19.2R2, 19.3R1 and above prior to 20.2R1. Juniper Networks Junos OS Evolved versions prior to 20.2R1-EVO.

Affected

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

Vendor states this is fixed in 19.2 (unaffected)
Vendor states this is fixed in 19.3R1 (unaffected)
Vendor states this is fixed in 19.4R1 (unaffected)
Vendor states this is fixed in 20.1R1 (unaffected)
Affected range stops below 20.2R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.3R3-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.4R3-S4, 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.2R2, 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-S4-EVO21.1R1-EVO ≤ v < 21.1-EVO*21.2-EVO ≤ v < 21.2R2-EVO21.3-EVO ≤ v < 21.3R2-EVO21.1R1-EVO21.2-EVO21.3-EVO
Vendor states this is fixed in 20.2R1-EVO (unaffected)
Affected range stops below 20.4R3-S4-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.2R2-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.9MEDIUMjuniper
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-367

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