CVE-2021-31362

Junos OS and Junos OS Evolved: An IS-IS adjacency might be taken down if a bad hello PDU is received for an existing adjacency causing a DoS

MEDIUM

6.5

CVSS Score

Published: October 19, 2021 at 06:16 PM UTC

Updated: June 17, 2026 at 03:51 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

MEDIUM6.5

Exploit prediction

EPSS 0.4%

Description

A Protection Mechanism Failure vulnerability in RPD (routing protocol daemon) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent unauthenticated attacker to cause established IS-IS adjacencies to go down by sending a spoofed hello PDU leading to a Denial of Service (DoS) condition. Continued receipted of these spoofed PDUs will create a sustained Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS All versions prior to 18.2R3-S8; 18.3 versions prior to 18.3R3-S5; 18.4 versions prior to 18.4R3-S9; 19.1 versions prior to 19.1R3-S7; 19.2 versions prior to 19.2R1-S7, 19.2R3-S3; 19.3 versions prior to 19.3R2-S6, 19.3R3-S2; 19.4 versions prior to 19.4R3-S3; 20.1 versions prior to 20.1R3; 20.2 versions prior to 20.2R3; 20.3 versions prior to 20.3R3; 20.4 versions prior to 20.4R2. Juniper Networks Junos OS Evolved All versions prior to 20.4R2-EVO; 21.1 versions prior to 21.1R2-EVO.

Affected

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

Junos OS Evolved · Juniper

95%

v ≤ 20.320.4 r1 20.4 r1-s1 20.4 r1-s2 21.1 21.1 r1 21.1 r1-s1

Junos · Juniper Networks

95%

v ≤ 18.1v < 18.2R3-S818.3 ≤ v < 18.3R3-S518.4 ≤ v < 18.4R3-S919.1 ≤ v < 19.1R3-S719.2 ≤ v < 19.2R1-S7, 19.2R3-S319.3 ≤ v < 19.3R2-S6, 19.3R3-S219.4 ≤ v < 19.4R3-S320.1 ≤ v < 20.1R320.2 ≤ v < 20.2R320.3 ≤ v < 20.3R320.4 ≤ v < 20.4R218.2 18.2 r1 18.2 r1-s2 18.2 r1-s3 18.2 r1-s4 18.2 r1-s5 18.2 r2 18.2 r2-s1 18.2 r2-s2 18.2 r2-s3 18.2 r2-s4 18.2 r2-s5 18.2 r2-s6 18.2 r2-s7 18.2 r3 18.2 r3-s1 18.2 r3-s2 18.2 r3-s3 18.2 r3-s4 18.2 r3-s5 18.2 r3-s6 18.2 r3-s7 18.3 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.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 r3 18.4 r3-s1 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 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 r2 19.2 r2-s1 19.2 r3 19.2 r3-s1 19.2 r3-s2 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 r3 19.3 r3-s1 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 r3 19.4 r3-s1 19.4 r3-s2 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.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.3 20.3 r1 20.3 r1-s1 20.3 r2 20.3 r2-s1 20.4 20.4 r1 20.4 r1-s1

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

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

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

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

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

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

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

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

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

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

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

Junos OS Evolved · Juniper Networks

60%

v < 20.4R2-EVO21.1 ≤ v < 21.1R2-EVO21.1

Affected range stops below 20.4R2-EVO, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.1R2-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/JSA11224

References (1)

x_refsource_CONFIRMVendor Advisory

Source: [email protected]

https://kb.juniper.net/JSA11224

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-693NVD-CWE-Other

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