CVE-2022-22161

Junos OS: MX104 might become unresponsive if the out-of-band management port receives a flood of traffic

HIGH

7.5

CVSS Score

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

Updated: June 17, 2026 at 04:27 AM UTC

2 products affected across 2 vendorsJunosMx104

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

HIGH7.5

Exploit prediction

EPSS 1.0%

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 an irq handled by the fman process is shown to be using a high percentage of CPU cycles like in the following example output: user@host> show system processes extensive ... PID USERNAME PRI NICE SIZE RES STATE TIME WCPU COMMAND 31 root -84 -187 0K 16K WAIT 22.2H 56939.26% irq96: fman0 This issue affects Juniper Networks Junos OS: All versions prior to 18.3R3-S6; 18.4 versions prior to 18.4R2-S9, 18.4R3-S9; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S7, 19.2R3-S3; 19.3 versions prior to 19.3R2-S7, 19.3R3-S4; 19.4 versions prior to 19.4R2-S5, 19.4R3-S5; 20.1 versions prior to 20.1R3-S1; 20.2 versions prior to 20.2R3-S2; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R2-S2, 20.4R3; 21.1 versions prior to 21.1R2; 21.2 versions prior to 21.2R1-S1, 21.2R2.

Affected

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

Junos · Juniper Networks

95%

v ≤ 18.2v < 18.3R3-S618.4 ≤ v < 18.4R2-S9, 18.4R3-S919.1 ≤ v < 19.1R2-S3, 19.1R3-S719.2 ≤ v < 19.2R1-S7, 19.2R3-S319.3 ≤ v < 19.3R2-S7, 19.3R3-S419.4 ≤ v < 19.4R2-S5, 19.4R3-S520.1 ≤ v < 20.1R3-S120.2 ≤ v < 20.2R3-S220.3 ≤ v < 20.3R3-S120.4 ≤ v < 20.4R2-S2, 20.4R321.1 ≤ v < 21.1R221.2 ≤ v < 21.2R1-S1, 21.2R218.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 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 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 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 r3 19.4 r3-s1 19.4 r3-s2 19.4 r3-s3 19.4 r3-s4 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.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.3 20.3 r1 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 21.1 21.1 r1 21.1 r1-s1 21.2 21.2 r1

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-S9, 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-S3, 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.4R2-S5, 19.4R3-S5, 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-S2, 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.1R2, 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

juniper-mx104 (environment)

Mx104 · Juniperdevice

80%

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

https://kb.juniper.net/JSA11269

References (1)

x_refsource_CONFIRMVendor Advisory

Source: [email protected]

https://kb.juniper.net/JSA11269

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.

Create account Sign in

Free plan, no card