On Juniper Networks MX Series and EX9200 Series platforms with Trio-based MPC (Modular Port Concentrator) where Integrated Routing and Bridging (IRB) interface is configured and it is mapped to a VPLS instance or a Bridge-Domain, certain network events at Customer Edge (CE) device may cause memory leak in the MPC which can cause an out of memory and MPC restarts. 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). Please refer to https://kb.juniper.net/KB25385 for the list of Trio-based PFEs. This issue affects Juniper Networks Junos OS on MX Series, EX9200 Series: 17.3R3-S8; 17.4R3-S2; 18.2R3-S4, 18.2R3-S5; 18.3R3-S2, 18.3R3-S3; 18.4 versions starting from 18.4R3-S1 and later versions prior to 18.4R3-S6; 19.2 versions starting from 19.2R2 and later versions prior to 19.2R3-S1; 19.4 versions starting from 19.4R2 and later versions prior to 19.4R2-S3, 19.4R3; 20.2 versions starting from 20.2R1 and later versions prior to 20.2R1-S3, 20.2R2. This issue does not affect Juniper Networks Junos OS: 18.1, 19.1, 19.3, 20.1.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.5, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts and availability (service disruption) for affected systems. Impacting 17 products from juniper, from juniper, from juniper and 14 others, organizations running these solutions should prioritize assessment and patching.
Reported in 2021, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2021-01-15T18:15:14.370
2024-11-21T05:42:11.437
Modified
CVSSv3.1: 7.5 (HIGH)
AV:N/AC:L/Au:N/C:N/I:N/A:P
10.0
2.9
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Operating System | juniper | junos | 17.3 | Yes |
| Operating System | juniper | junos | 17.4 | Yes |
| Operating System | juniper | junos | 18.2 | Yes |
| Operating System | juniper | junos | 18.2 | Yes |
| Operating System | juniper | junos | 18.3 | Yes |
| Operating System | juniper | junos | 18.3 | Yes |
| Operating System | juniper | junos | 18.4 | Yes |
| Operating System | juniper | junos | 18.4 | Yes |
| Operating System | juniper | junos | 18.4 | Yes |
| Operating System | juniper | junos | 18.4 | Yes |
| Operating System | juniper | junos | 18.4 | Yes |
| Operating System | juniper | junos | 19.2 | Yes |
| Operating System | juniper | junos | 19.2 | Yes |
| Operating System | juniper | junos | 19.4 | Yes |
| Operating System | juniper | junos | 19.4 | Yes |
| Operating System | juniper | junos | 19.4 | Yes |
| Operating System | juniper | junos | 20.2 | Yes |
| Operating System | juniper | junos | 20.2 | Yes |
| Operating System | juniper | junos | 20.2 | Yes |
| Hardware | juniper | ex9200 | - | No |
| Hardware | juniper | mx10 | - | No |
| Hardware | juniper | mx10000 | - | No |
| Hardware | juniper | mx10003 | - | No |
| Hardware | juniper | mx104 | - | No |
| Hardware | juniper | mx150 | - | No |
| Hardware | juniper | mx2008 | - | No |
| Hardware | juniper | mx2010 | - | No |
| Hardware | juniper | mx2020 | - | No |
| Hardware | juniper | mx204 | - | No |
| Hardware | juniper | mx240 | - | No |
| Hardware | juniper | mx40 | - | No |
| Hardware | juniper | mx480 | - | No |
| Hardware | juniper | mx5 | - | No |
| Hardware | juniper | mx80 | - | No |
| Hardware | juniper | mx960 | - | No |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For juniper's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.