CVE-2023-22407

Junos OS and Junos OS Evolved: An RPD crash can happen due to an MPLS TE tunnel configuration change on a directly connected router

MEDIUM
6.5
CVSS Score
Published: January 12, 2023 at 12:00 AM UTC
Updated: June 17, 2026 at 05:35 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
MEDIUM6.5
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

An Incomplete Cleanup vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent, unauthenticated attacker to cause a Denial of Service (DoS). An rpd crash can occur when an MPLS TE tunnel configuration change occurs on a directly connected router. This issue affects: Juniper Networks Junos OS All versions prior to 18.4R2-S7; 19.1 versions prior to 19.1R3-S2; 19.2 versions prior to 19.2R3; 19.3 versions prior to 19.3R3; 19.4 versions prior to 19.4R3; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R2. Juniper Networks Junos OS Evolved All versions prior to 19.2R3-EVO; 19.3 versions prior to 19.3R3-EVO; 19.4 versions prior to 19.4R3-EVO; 20.1 versions prior to 20.1R3-EVO; 20.2 versions prior to 20.2R2-EVO.

Affected

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

Affected range stops below 18.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.4R2-S7, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.1R3-S2, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.2R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.3R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.4R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.1R2, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.2R2, so it looks safe — our inference, not a vendor statement
v < 19.2R3-EVO19.3 ≤ v < 19.3R3-EVO19.4 ≤ v < 19.4R3-EVO20.1 ≤ v < 20.1R3-EVO20.2 ≤ v < 20.2R2-EVO19.319.420.120.2
Affected range stops below 19.2R3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.3R3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.4R3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.1R3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.2R2-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

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

Quick Info

StatusMODIFIED
CWE
CWE-459

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