CVE-2021-0258

Junos OS: Kernel panic upon receipt of specific TCPv6 packet on management interface

MEDIUM

5.9

CVSS Score

Published: April 22, 2021 at 07:37 PM UTC

Updated: June 17, 2026 at 03:29 AM UTC

1 product affected across 1 vendorJunos

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.6%

Description

A vulnerability in the forwarding of transit TCPv6 packets received on the Ethernet management interface of Juniper Networks Junos OS allows an attacker to trigger a kernel panic, leading to a Denial of Service (DoS). Continued receipt and processing of these transit packets will create a sustained Denial of Service (DoS) condition. This issue only occurs when TCPv6 packets are routed through the management interface. Other transit traffic, and traffic destined to the management interface, are unaffected by this vulnerability. This issue was introduced as part of a TCP Parallelization feature added in Junos OS 17.2, and affects systems with concurrent network stack enabled. This feature is enabled by default, but can be disabled (see WORKAROUND section below). This issue affects Juniper Networks Junos OS: 17.2 versions prior to 17.2R3-S4; 17.3 versions prior to 17.3R3-S9; 17.4 versions prior to 17.4R2-S11, 17.4R3-S2; 18.1 versions prior to 18.1R3-S11; 18.2 versions prior to 18.2R3-S5; 18.3 versions prior to 18.3R2-S4, 18.3R3-S3; 18.4 versions prior to 18.4R2-S5, 18.4R3-S4; 19.1 versions prior to 19.1R2-S2, 19.1R3; 19.2 versions prior to 19.2R1-S5, 19.2R2; 19.3 versions prior to 19.3R2-S4, 19.3R3; 19.4 versions prior to 19.4R1-S3, 19.4R2. This issue does not affect Juniper Networks Junos OS versions prior to 17.2R1.

Affected

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

Junos · Juniper Networks

95%

17.3 ≤ v < 17.3R3-S917.4 ≤ v < 17.4R2-S11, 17.4R3-S218.1 ≤ v < 18.1R3-S1118.2 ≤ v < 18.2R3-S518.3 ≤ v < 18.3R2-S4, 18.3R3-S318.4 ≤ v < 18.4R2-S5, 18.4R3-S419.1 ≤ v < 19.1R2-S2, 19.1R319.2 ≤ v < 19.2R1-S5, 19.2R219.3 ≤ v < 19.3R2-S4, 19.3R319.4 ≤ v < 19.4R1-S3, 19.4R217.2 17.2 r1 17.2 r1-s1 17.2 r1-s2 17.2 r1-s3 17.2 r1-s4 17.2 r1-s5 17.2 r1-s6 17.2 r1-s7 17.2 r1-s8 17.2 r2 17.2 r2-s11 17.2 r2-s4 17.2 r2-s6 17.2 r2-s7 17.2 r3 17.2 r3-s1 17.2 r3-s2 17.2 r3-s3 17.3 17.3 r1 17.3 r1-s1 17.3 r1-s4 17.3 r2 17.3 r2-s1 17.3 r2-s2 17.3 r2-s3 17.3 r2-s4 17.3 r2-s5 17.3 r3 17.3 r3-s1 17.3 r3-s10 17.3 r3-s2 17.3 r3-s3 17.3 r3-s4 17.3 r3-s5 17.3 r3-s6 17.3 r3-s7 17.3 r3-s8 17.4 17.4 r1 17.4 r1-s1 17.4 r1-s2 17.4 r1-s3 17.4 r1-s4 17.4 r1-s5 17.4 r1-s6 17.4 r1-s7 17.4 r2 17.4 r2-s1 17.4 r2-s10 17.4 r2-s2 17.4 r2-s3 17.4 r2-s4 17.4 r2-s5 17.4 r2-s6 17.4 r2-s7 17.4 r2-s8 17.4 r2-s9 17.4 r3 17.4 r3-s1 18.1 18.1 r1 18.1 r2 18.1 r2-s1 18.1 r2-s2 18.1 r2-s4 18.1 r3 18.1 r3-s1 18.1 r3-s10 18.1 r3-s2 18.1 r3-s3 18.1 r3-s4 18.1 r3-s5 18.1 r3-s6 18.1 r3-s7 18.1 r3-s8 18.1 r3-s9 18.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.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 r3 18.3 r3-s1 18.3 r3-s2 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 r3 18.4 r3-s1 18.4 r3-s2 18.4 r3-s3 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 r2 19.1 r2-s1 19.2 19.2 r1 19.2 r1-s1 19.2 r1-s2 19.2 r1-s3 19.2 r1-s4 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.4 19.4 r1 19.4 r1-s1 19.4 r1-s2

Vendor states this is fixed in 17.2 (unaffected)

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

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

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

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

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

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

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

Affected range stops below 19.2R1-S5, 19.2R2, so it looks safe — our inference, not a vendor statement

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

Affected range stops below 19.4R1-S3, 19.4R2, 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/JSA11149

References (1)

x_refsource_MISCVendor Advisory

Source: [email protected]

https://kb.juniper.net/JSA11149

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

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