CVE-2021-0238

Junos OS: MX Series: Executing CLI command repetitively may cause the system to run out of disk space

MEDIUM
5.5
CVSS Score
Published: April 22, 2021 at 07:37 PM UTC
Updated: June 17, 2026 at 03:29 AM UTC
15 products affected across 2 vendorsJunosMx480Mx960

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
MEDIUM5.5
Exploit prediction
EPSS 0.2%

Description

When a MX Series is configured as a Broadband Network Gateway (BNG) based on Layer 2 Tunneling Protocol (L2TP), executing certain CLI command may cause the system to run out of disk space, excessive disk usage may cause other complications. An administrator can use the following CLI command to monitor the available disk space: user@device> show system storage Filesystem Size Used Avail Capacity Mounted on /dev/gpt/junos 19G 18G 147M 99% /.mount <<<<< running out of space tmpfs 21G 16K 21G 0% /.mount/tmp tmpfs 5.3G 1.7M 5.3G 0% /.mount/mfs This issue affects Juniper Networks Junos OS on MX Series: 17.3R1 and later versions prior to 17.4R3-S5, 18.1 versions prior to 18.1R3-S13, 18.2 versions prior to 18.2R3-S7; 18.3 versions prior to 18.3R3-S4; 18.4 versions prior to 18.4R3-S7; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R1-S6, 19.2R3-S2; 19.3 versions prior to 19.3R3-S2; 19.4 versions prior to 19.4R2-S4, 19.4R3-S2; 20.1 versions prior to 20.1R3; 20.2 versions prior to 20.2R2-S3, 20.2R3; 20.3 versions prior to 20.3R2; 20.4 versions prior to 20.4R1-S1, 20.4R2; This issue does not affect Juniper Networks Junos OS versions prior to 17.3R1.

Affected

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

17.3R1 ≤ v < 17.3*17.4 ≤ v < 17.4R3-S518.1 ≤ v < 18.1R3-S1318.2 ≤ v < 18.2R3-S718.3 ≤ v < 18.3R3-S418.4 ≤ v < 18.4R3-S719.1 ≤ v < 19.1R3-S419.2 ≤ v < 19.2R1-S6, 19.2R3-S219.3 ≤ v < 19.3R3-S219.4 ≤ v < 19.4R2-S4, 19.4R3-S220.1 ≤ v < 20.1R320.2 ≤ v < 20.2R2-S3, 20.2R320.3 ≤ v < 20.3R220.4 ≤ v < 20.4R1-S1, 20.4R217.3 r117.3 r1-s117.3 r1-s417.3 r217.3 r2-s117.3 r2-s217.3 r2-s317.3 r2-s417.3 r2-s517.3 r317.3 r3-s117.3 r3-s1017.3 r3-s217.3 r3-s317.3 r3-s417.3R117.418.118.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 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 r318.2 r3-s118.2 r3-s218.2 r3-s318.2 r3-s418.2 r3-s518.2 r3-s618.318.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.419.119.1 r119.1 r1-s119.1 r1-s219.1 r1-s319.1 r1-s419.1 r1-s519.1 r219.1 r2-s119.1 r319.1 r3-s119.1 r3-s219.1 r3-s319.219.2 r119.2 r1-s119.2 r1-s219.2 r1-s319.2 r1-s419.2 r1-s519.2 r219.2 r2-s119.2 r319.2 r3-s119.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.419.4 r119.4 r1-s119.4 r1-s219.4 r219.4 r2-s119.4 r2-s219.4 r2-s319.4 r319.4 r3-s120.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.320.3 r120.420.4 r1
Affected range stops below 17.3*, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 17.3R1 (unaffected)
Affected range stops below 17.4R3-S5, 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-S7, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.3R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.4R3-S7, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.1R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.2R1-S6, 19.2R3-S2, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.3R3-S2, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.4R2-S4, 19.4R3-S2, 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.2R2-S3, 20.2R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.3R2, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.4R1-S1, 20.4R2, so it looks safe — our inference, not a vendor statement
juniper-mx10 (environment) · juniper-mx10000 (environment) · juniper-mx10003 (environment) · juniper-mx104 (environment) · juniper-mx150 (environment) · juniper-mx2008 (environment) · juniper-mx2010 (environment) · juniper-mx2020 (environment) · juniper-mx204 (environment) · juniper-mx40 (environment) · juniper-mx480 (environment) · juniper-mx5 (environment) · juniper-mx80 (environment) · juniper-mx960 (environment)
All versions
All versions
All versions
All versions
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_MISCVendor Advisory
https://kb.juniper.net/JSA11133

CVSS

5.5MEDIUMjuniper
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
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