CVE-2022-22169

Junos OS and Junos OS Evolved: OSPFv3 session might go into INIT state upon receipt of multiple crafted packets from a trusted neighbor device.

MEDIUM

5.9

CVSS Score

Published: January 19, 2022 at 12:21 AM UTC

Updated: June 17, 2026 at 04:27 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

Start Free Sign In

Severity

MEDIUM5.9

Exploit prediction

EPSS 0.8%

Description

An Improper Initialization vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an attacker who sends specific packets in certain orders and at specific timings to force OSPFv3 to unexpectedly enter graceful-restart (GR helper mode) even though there is not any Grace-LSA received in OSPFv3 causing a Denial of Service (DoS). Unexpectedly entering GR helper mode might cause the OSPFv3 neighbor adjacency formed on this interface to be stuck in the "INIT" state which can be observed by issuing the following command: user@device> show ospf3 neighbor ID Interface State xx.xx.xx.xx ae100.0 Init <<<<<<<<<< An indicator of compromise can be seen in log files when traceoptions for OSPFv3 are enabled before the issue occurs. These logfile messages are as follows: OSPF restart signaling: Received hello with LR bit set from nbr ip=xx::xx id=xx.xx.xx.xx. Set oob-resync capabilty 1. OSPF Restart Signaling: Start helper mode for nbr ip xx::xx id xx.xx.xx.xx OSPF restart signaling: abort helper mode for nbr ip=xx::xx id=xx.xx.xx.xx OSPF neighbor xx::xx (realm ipv6-unicast <interface.unit> area xx.xx.xx.xx) state changed from Full to Init due to 1WayRcvd (event reason: neighbor is in one-way mode) (nbr helped: 0) This issue affects: Juniper Networks Junos OS. 15.1 versions prior to 15.1R7-S11; 18.3 versions prior to 18.3R3-S6; 18.4 versions prior to 18.4R2-S9, 18.4R3-S10; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S7, 19.2R3-S4; 19.3 versions prior to 19.3R2-S7, 19.3R3-S4; 19.4 versions prior to 19.4R3-S6; 20.1 versions prior to 20.1R3-S1; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R2-S2, 20.4R3; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R1-S1, 21.2R2. This issue does not affect any version of Juniper Networks Junos OS 12.3. This issue affects Juniper Networks Junos OS Evolved all versions prior to 21.2R2-EVO.

Affected

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

Junos OS Evolved · Juniper

95%

v < 21.221.2 21.2 r1 21.2 r1-s1 21.2 r1-s2

Affected range stops below 21.2, so it looks safe — our inference, not a vendor statement

Junos · Juniper Networks

95%

15.1 ≤ v < 15.1R7-S1118.3 ≤ v < 18.3R3-S618.4 ≤ v < 18.4R2-S9, 18.4R3-S1019.1 ≤ v < 19.1R2-S3, 19.1R3-S719.2 ≤ v < 19.2R1-S7, 19.2R3-S419.3 ≤ v < 19.3R2-S7, 19.3R3-S419.4 ≤ v < 19.4R3-S620.1 ≤ v < 20.1R3-S120.2 ≤ v < 20.2R3-S320.3 ≤ v < 20.3R3-S120.4 ≤ v < 20.4R2-S2, 20.4R321.1 ≤ v < 21.1R321.2 ≤ v < 21.2R1-S1, 21.2R215.1 15.1 a1 15.1 f 15.1 f1 15.1 f2 15.1 f2-s1 15.1 f2-s2 15.1 f2-s3 15.1 f2-s4 15.1 f3 15.1 f4 15.1 f5 15.1 f5-s7 15.1 f6 15.1 f6-s1 15.1 f6-s10 15.1 f6-s12 15.1 f6-s2 15.1 f6-s3 15.1 f6-s4 15.1 f6-s5 15.1 f6-s6 15.1 f6-s7 15.1 f6-s8 15.1 f6-s9 15.1 f7 15.1 r 15.1 r1 15.1 r2 15.1 r3 15.1 r4 15.1 r4-s7 15.1 r4-s8 15.1 r4-s9 15.1 r5 15.1 r5-s1 15.1 r5-s3 15.1 r5-s5 15.1 r5-s6 15.1 r6 15.1 r6-s1 15.1 r6-s2 15.1 r6-s3 15.1 r6-s4 15.1 r6-s6 15.1 r7 15.1 r7-s1 15.1 r7-s10 15.1 r7-s2 15.1 r7-s3 15.1 r7-s4 15.1 r7-s5 15.1 r7-s6 15.1 r7-s7 15.1 r7-s8 15.1 r7-s9 18.3 18.3 r 18.3 r1 18.3 r1-s1 18.3 r1-s2 18.3 r1-s3 18.3 r1-s4 18.3 r1-s5 18.3 r1-s6 18.3 r2 18.3 r2-s1 18.3 r2-s2 18.3 r2-s3 18.3 r2-s4 18.3 r3 18.3 r3-s1 18.3 r3-s2 18.3 r3-s3 18.3 r3-s4 18.3 r3-s5 18.4 18.4 r1 18.4 r1-s1 18.4 r1-s2 18.4 r1-s3 18.4 r1-s4 18.4 r1-s5 18.4 r1-s6 18.4 r1-s7 18.4 r2 18.4 r2-s1 18.4 r2-s2 18.4 r2-s3 18.4 r2-s4 18.4 r2-s5 18.4 r2-s6 18.4 r2-s7 18.4 r2-s8 18.4 r2-s9 18.4 r3 18.4 r3-s1 18.4 r3-s10 18.4 r3-s2 18.4 r3-s3 18.4 r3-s4 18.4 r3-s5 18.4 r3-s6 18.4 r3-s7 18.4 r3-s8 18.4 r3-s9 19.1 19.1 r1 19.1 r1-s1 19.1 r1-s2 19.1 r1-s3 19.1 r1-s4 19.1 r1-s5 19.1 r1-s6 19.1 r2 19.1 r2-s1 19.1 r2-s2 19.1 r3 19.1 r3-s1 19.1 r3-s2 19.1 r3-s3 19.1 r3-s4 19.1 r3-s5 19.1 r3-s6 19.2 19.2 r1 19.2 r1-s1 19.2 r1-s2 19.2 r1-s3 19.2 r1-s4 19.2 r1-s5 19.2 r1-s6 19.2 r3 19.2 r3-s1 19.2 r3-s2 19.2 r3-s3 19.3 19.3 r1 19.3 r1-s1 19.3 r2 19.3 r2-s1 19.3 r2-s2 19.3 r2-s3 19.3 r2-s4 19.3 r2-s5 19.3 r2-s6 19.3 r3 19.3 r3-s1 19.3 r3-s2 19.3 r3-s3 19.4 19.4 r1 19.4 r1-s1 19.4 r1-s2 19.4 r1-s3 19.4 r1-s4 19.4 r2 19.4 r2-s1 19.4 r2-s2 19.4 r2-s3 19.4 r2-s4 19.4 r2-s5 19.4 r3 19.4 r3-s1 19.4 r3-s2 19.4 r3-s3 19.4 r3-s4 19.4 r3-s5 20.1 20.1 r1 20.1 r1-s1 20.1 r1-s2 20.1 r1-s3 20.1 r1-s4 20.1 r2 20.1 r2-s1 20.1 r2-s2 20.1 r3 20.1 r3-s1 20.1 r3-s2 20.2 20.2 r1 20.2 r1-s1 20.2 r1-s2 20.2 r1-s3 20.2 r2 20.2 r2-s1 20.2 r2-s2 20.2 r2-s3 20.2 r3 20.2 r3-s1 20.2 r3-s2 20.3 20.3 r1 20.3 r1-s1 20.3 r2 20.3 r2-s1 20.3 r3 20.4 20.4 r1 20.4 r1-s1 20.4 r2 20.4 r2-s1 20.4 r2-s2 21.1 21.1 r1 21.1 r1-s1 21.1 r2 21.2 21.2 r1

Vendor states this is fixed in 12.3 Any (unaffected)

Affected range stops below 15.1R7-S11, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.3R3-S6, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.4R2-S9, 18.4R3-S10, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.1R2-S3, 19.1R3-S7, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.2R1-S7, 19.2R3-S4, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.3R2-S7, 19.3R3-S4, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.4R3-S6, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.1R3-S1, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.2R3-S3, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.3R3-S1, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.4R2-S2, 20.4R3, 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-S1, 21.2R2, so it looks safe — our inference, not a vendor statement

Junos OS Evolved · Juniper Networks

60%

v < 21.2R2-EVO

Affected range stops below 21.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

https://kb.juniper.net/JSA11276

References (1)

x_refsource_CONFIRMVendor Advisory

Source: [email protected]

https://kb.juniper.net/JSA11276

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-665

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.

Create account Sign in

Free plan, no card