LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a service availability risk in specific Juniper MX and EX9200 routing platforms. Certain customer-edge Layer 2 events can leak memory on Trio-based line cards when IRB is tied to VPLS or a bridge-domain. If memory is exhausted, the MPC can restart, causing temporary traffic interruption.

Executive priority

Treat as a moderate operational risk where affected Juniper PE routers support important customer services. It is not described as data theft or privilege compromise, but an MPC restart can interrupt traffic. Prioritize remediation for high-value network segments and heavily used VPLS environments.

Technical view

Affected Junos OS releases on MX Series and EX9200 Series with Trio-based MPC/PFEs can leak next-hop memory under specific IRB plus VPLS or bridge-domain configurations. The issue is CWE-400 resource consumption, CVSS 6.5, adjacent-network, no authentication required, with high availability impact and no confidentiality or integrity impact.

Likely exposure

Exposure is limited to Juniper MX Series and EX9200 Series using listed Trio-based MPCs/PFEs with IRB interfaces mapped to VPLS instances or bridge-domains on affected Junos OS versions. The vendor states no other products or platforms are affected.

Exploitation context

The source bundle does not cite active exploitation, and the CVE is not marked KEV. Triggering requires relevant Layer 2 network events at customer-edge devices and adjacency to the affected network context, so this is mainly an outage and resilience concern for provider-edge environments.

Researcher notes

The advisory scope is narrow: Trio-based MPC/PFE platforms, IRB mapped to VPLS or bridge-domain, and specified Junos trains. The observable failure mode is next-hop memory depletion followed by MPC restart. Evidence provided does not establish public exploitation or broader platform impact.

Mitigation direction

  • Upgrade affected Junos OS trains to Juniper's listed fixed releases or later.
  • Prioritize PE devices carrying critical VPLS or bridge-domain services.
  • Review Juniper JSA11148 for exact fixed releases and operational guidance.
  • Monitor affected MPC memory until remediation is complete.
  • Plan maintenance windows for upgrades because PE line-card restarts affect traffic.

Validation and detection

  • Inventory MX and EX9200 devices with Trio-based MPCs or PFEs.
  • Identify IRB interfaces mapped to VPLS instances or bridge-domains.
  • Compare Junos OS versions against the affected and fixed release ranges.
  • Monitor FPC resource output for declining % NH mem Free.
  • Review device history for MPC restarts and related traffic interruptions.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-0257 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2021-0257Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Juniper NetworksJunos OS17.3, 17.4, 18.2, 18.3, 18.4, 19.2, 19.3, 19.4, 20.2, 20.3Listed
Juniper NetworksJunos OS18.1, 19.1, 17.3, 17.4, 18.2, 18.3, 18.4, 19.2, 19.3, 19.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.