02 Records
FEED: ACQUIRING
01 RecordSTATE: PUBLISHED
02 Description
CNA: juniperJunos OS: MX Series, EX9200 Series: Trio-based MPC memory leak when Integrated Routing and Bridging (IRB) interface is mapped to a VPLS instance or a Bridge-Domain
03 Exploitation and scoring
SRC: CISA, FIRST, NVD, RED HAT- Exploitation
- Not assessed. CISA has not published an exploitation assessment for this record, and it is not in the KEV catalog. That is an absence of assessment, not a finding of no risk.
- SSVC decision
- Not assessed by CISA
- EPSS probability
- 1.03% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Ranks above 61.2% of scored records. A rank, not a probability.
- NVD base score
- 7.5 (CVSS v3.x), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- NVD analysis status
- Modified. NVD last modified this record on 2026-06-17.
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
SCHEMA: 5.1
- Published
- 2021-01-15 17:35Z5 YR AGO
- Last updated
- 2024-09-17 00:31Z1 YR AGO
- Reserved
- 2020-10-27
- Assigning CNA
- juniper
- Record state
- PUBLISHED
- Severity
- High (CVSS 7.5)
- CNA CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-400Uncontrolled Resource ConsumptionClass
- CWE-401Missing Release of Memory after Effective LifetimeVariant
- Data version
- 5.1
- Document digest
- 6c062b10299d054a4151c5b5b4c0082d6602cd431964f9743ca0aa93284b101f
05 Affected products
PAIRS: 1VendorProductVersionsPlatforms
Juniper NetworksJunos OS17.3R3-S8, 17.4R3-S2, 18.2R3-S4 to < 18.2*, 18.3R3-S2 to < 18.3*, 18.4R3-S1 to < 18.4*, 19.2R2 to < 19.2*, 19.4R2 to < 19.4*, 20.2R1 to < 20.2*MX Series, EX9200 Series SRC: CNA
The following software releases have been updated to resolve this specific issue: 17.3R3-S9, 17.4R3-S3, 18.2R3-S6, 18.3R3-S4, 18.4R3-S6, 19.2R3-S1, 19.4R2-S3, 19.4R3, 20.2R1-S3, 20.2R2, 20.3R1, and all subsequent releases.
The fix has been proactively committed to other releases as well.