CVE-2021-31368

Junos OS: EX2300 Series, EX3400 Series, and ACX710 might become unresponsive if the out-of-band management port receives a flood of traffic

HIGH
7.5
CVSS Score
Published: October 19, 2021 at 06:16 PM UTC
Updated: June 17, 2026 at 03:51 AM UTC
6 products affected across 2 vendorsJunosEx2300Ex3400

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
HIGH7.5
Exploit prediction
EPSS 1%

Description

An Uncontrolled Resource Consumption vulnerability in the kernel of Juniper Networks JUNOS OS allows an unauthenticated network based attacker to cause 100% CPU load and the device to become unresponsive by sending a flood of traffic to the out-of-band management ethernet port. Continued receipted of a flood will create a sustained Denial of Service (DoS) condition. Once the flood subsides the system will recover by itself. An indication that the system is affected by this issue would be that kernel and netisr process are shown to be using a lot of CPU cycles like in the following example output: user@host> show system processes extensive ... PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 16 root -72 - 0K 304K WAIT 1 839:40 88.96% intr{swi1: netisr 0} 0 root 97 - 0K 160K RUN 1 732:43 87.99% kernel{bcm560xgmac0 que} This issue affects Juniper Networks JUNOS OS on EX2300 Series, EX3400 Series, and ACX710: All versions prior to 18.1R3-S13; 18.2 versions prior to 18.2R3-S8; 18.3 versions prior to 18.3R3-S5; 18.4 versions prior to 18.4R2-S8, 18.4R3-S9; 19.1 versions prior to 19.1R3-S5; 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.4R1-S4, 19.4R3-S3; 20.1 versions prior to 20.1R2-S2, 20.1R3; 20.2 versions prior to 20.2R3; 20.3 versions prior to 20.3R2-S1, 20.3R3; 20.4 versions prior to 20.4R2.

Affected

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

v < 18.1v < 18.1R3-S1318.2 ≤ v < 18.2R3-S818.3 ≤ v < 18.3R3-S518.4 ≤ v < 18.4R2-S8, 18.4R3-S919.1 ≤ v < 19.1R3-S519.2 ≤ v < 19.2R1-S7, 19.2R3-S319.3 ≤ v < 19.3R2-S6, 19.3R3-S219.4 ≤ v < 19.4R1-S4, 19.4R3-S320.1 ≤ v < 20.1R2-S2, 20.1R320.2 ≤ v < 20.2R320.3 ≤ v < 20.3R2-S1, 20.3R320.4 ≤ v < 20.4R218.118.1 r18.1 r118.1 r218.1 r2-s118.1 r2-s218.1 r2-s418.1 r318.1 r3-s118.1 r3-s1018.1 r3-s1118.1 r3-s1218.1 r3-s218.1 r3-s318.1 r3-s418.1 r3-s518.1 r3-s618.1 r3-s718.1 r3-s818.1 r3-s918.218.2 r18.2 r118.2 r1-s218.2 r1-s318.2 r1-s418.2 r1-s518.2 r218.2 r2-s118.2 r2-s218.2 r2-s318.2 r2-s418.2 r2-s518.2 r2-s618.2 r2-s718.2 r2-s818.2 r318.2 r3-s118.2 r3-s218.2 r3-s318.2 r3-s418.2 r3-s518.2 r3-s618.2 r3-s718.318.3 r18.3 r118.3 r1-s118.3 r1-s218.3 r1-s318.3 r1-s418.3 r1-s518.3 r1-s618.3 r218.3 r2-s118.3 r2-s218.3 r2-s318.3 r2-s418.3 r318.3 r3-s118.3 r3-s218.3 r3-s318.3 r3-s418.418.4 r118.4 r1-s118.4 r1-s218.4 r1-s318.4 r1-s418.4 r1-s518.4 r1-s618.4 r1-s718.4 r218.4 r2-s118.4 r2-s218.4 r2-s318.4 r2-s418.4 r2-s518.4 r2-s618.4 r2-s718.4 r318.4 r3-s118.4 r3-s218.4 r3-s318.4 r3-s418.4 r3-s518.4 r3-s618.4 r3-s718.4 r3-s819.119.1 r119.1 r1-s119.1 r1-s219.1 r1-s319.1 r1-s419.1 r1-s519.1 r1-s619.1 r219.1 r2-s119.1 r2-s219.1 r2-s319.1 r319.1 r3-s119.1 r3-s219.1 r3-s319.1 r3-s419.219.2 r119.2 r1-s119.2 r1-s219.2 r1-s319.2 r1-s419.2 r1-s519.2 r1-s619.2 r219.2 r2-s119.2 r319.2 r3-s119.2 r3-s219.319.3 r119.3 r1-s119.3 r219.3 r2-s119.3 r2-s219.3 r2-s319.3 r2-s419.3 r2-s519.3 r319.3 r3-s119.419.4 r119.4 r1-s119.4 r1-s219.4 r1-s319.4 r219.4 r2-s119.4 r2-s219.4 r2-s319.4 r2-s419.4 r2-s519.4 r319.4 r3-s119.4 r3-s220.120.1 r120.1 r1-s120.1 r1-s220.1 r1-s320.1 r1-s420.1 r220.1 r2-s120.220.2 r120.2 r1-s120.2 r1-s220.2 r1-s320.2 r220.2 r2-s120.2 r2-s220.2 r2-s320.320.3 r120.3 r1-s120.3 r220.420.4 r120.4 r1-s1
Affected range stops below 18.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.1R3-S13, so it looks safe — our inference, not a vendor statement
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.4R2-S8, 18.4R3-S9, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.1R3-S5, 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.4R1-S4, 19.4R3-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.1R2-S2, 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.3R2-S1, 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
juniper-acx710 (environment) · juniper-ex2300 (environment) · juniper-ex2300-c (environment) · juniper-ex2300m (environment) · juniper-ex3400 (environment)
All versions
All versions
All versions
All versions
All versions

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)

x_refsource_CONFIRMVendor Advisory
https://kb.juniper.net/JSA11230

CVSS

7.5HIGHjuniper
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-400

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