CVE-2021-0257

Junos OS: MX Series, EX9200 Series: Trio-based MPCs memory leak in VPLS with integrated routing and bridging (IRB) interface

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

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
MEDIUM6.5
Exploit prediction
EPSS 0.4%

Description

On Juniper Networks MX Series and EX9200 Series platforms with Trio-based MPCs (Modular Port Concentrators) where Integrated Routing and Bridging (IRB) interfaces are configured and mapped to a VPLS instance or a Bridge-Domain, certain Layer 2 network events at Customer Edge (CE) devices may cause memory leaks in the MPC of Provider Edge (PE) devices which can cause an out of memory condition and MPC restart. When this issue occurs, there will be temporary traffic interruption until the MPC is restored. An administrator can use the following CLI command to monitor the status of memory usage level of the MPC: user@device> show system resource-monitor fpc FPC Resource Usage Summary Free Heap Mem Watermark : 20 % Free NH Mem Watermark : 20 % Free Filter Mem Watermark : 20 % * - Watermark reached Slot # % Heap Free RTT Average RTT 1 87 PFE # % ENCAP mem Free % NH mem Free % FW mem Free 0 NA 88 99 1 NA 89 99 When the issue is occurring, the value of “% NH mem Free” will go down until the MPC restarts. This issue affects MX Series and EX9200 Series with Trio-based PFEs (Packet Forwarding Engines), including MX-MPC1-3D, MX-MPC1E-3D, MX-MPC2-3D, MX-MPC2E-3D, MPC-3D-16XGE, and CHAS-MXxx Series MPCs. No other products or platforms are affected by this issue. This issue affects Juniper Networks Junos OS on MX Series, EX9200 Series: 17.3 versions prior to 17.3R3-S10; 17.4 versions prior to 17.4R3-S3; 18.2 versions prior to 18.2R3-S7; 18.3 versions prior to 18.3R3-S4; 18.4 versions prior to 18.4R3-S6; 19.2 versions prior to 19.2R3-S2; 19.3 versions prior to 19.3R3-S1; 19.4 versions prior to 19.4R2-S2, 19.4R3; 20.2 versions prior to 20.2R1-S3, 20.2R2; 20.3 versions prior to 20.3R1-S1,, 20.3R2. This issue does not affect Juniper Networks Junos OS: 17.3 versions prior to 17.3R3-S8; 17.4 versions prior to 17.4R3-S2; 18.1; 18.2 versions prior to 18.2R3-S4; 18.3 versions prior to 18.3R3-S2; 18.4 versions prior to 18.4R3-S1; 19.1; 19.2 versions prior to 19.2R2; 19.3 versions prior to 19.3R3; 19.4 versions prior to 19.4R2.

Affected

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

Vendor states this is fixed in 17.3 (unaffected)
Affected range stops below 17.3R3-S10, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 17.4 (unaffected)
Affected range stops below 17.4R3-S3, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 18.1 (unaffected)
Vendor states this is fixed in 18.2 (unaffected)
Affected range stops below 18.2R3-S7, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 18.3 (unaffected)
Affected range stops below 18.3R3-S4, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 18.4 (unaffected)
Affected range stops below 18.4R3-S6, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 19.1 (unaffected)
Vendor states this is fixed in 19.2 (unaffected)
Affected range stops below 19.2R3-S2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 19.3 (unaffected)
Affected range stops below 19.3R3-S1, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 19.4 (unaffected)
Affected range stops below 20.2R1-S3, 20.2R2, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.3R1-S1,, 20.3R2, so it looks safe — our inference, not a vendor statement
juniper-ex9200 (environment) · juniper-mx10 (environment) · juniper-mx10003 (environment) · juniper-mx10008 (environment) · juniper-mx10016 (environment) · juniper-mx104 (environment) · juniper-mx150 (environment) · juniper-mx2008 (environment) · juniper-mx2010 (environment) · juniper-mx2020 (environment) · juniper-mx204 (environment) · juniper-mx240 (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/JSA11148

CVSS

6.5MEDIUMjuniper
Attack Vector
ADJACENT_NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-400CWE-401

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