01 Record
CVE-2022-22170
Junos OS: Specific packets over VXLAN cause FPC memory leak and ultimately reset
HighPUBLISHEDCNA: juniper
CNA base score7.5 CVSS v3.xCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
02 Description
Junos OS: Specific packets over VXLAN cause FPC memory leak and ultimately reset
03 Exploitation and scoring
- 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
- 0.93% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 60.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.
04 Metadata
- Published
- 2022-01-19 00:21Z4 YR AGO
- Last updated
- 2024-09-17 04:23Z2 YR AGO
- Reserved
- 2021-12-21
- 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-772Missing Release of Resource after Effective LifetimeBase
- Data version
- 5.1
- Document digest
- 029694330242135f217406565292ad3791e7a7eb51f9125743134be15ebd59fb
05 Affected products
VendorProductVersionsPlatforms
Juniper NetworksJunos OS19.4 to < 19.4R2-S6, 19.4R3-S6, 20.1 to < 20.1R3-S2, 20.2 to < 20.2R3-S3, 20.3 to < 20.3R3-S1, 20.4 to < 20.4R3, 21.1 to < 21.1R3, 21.2 to < 21.2R2—
06 References
- kb.juniper.nethttps://kb.juniper.net/JSA11277
07 Remediation
The following Junos OS software releases have been updated to resolve this specific issue: 19.4R2-S6, 19.4R3-S6, 20.1R3-S2, 20.2R3-S3, 20.3R3-S1, 20.4R3, 21.1R3, 21.2R2, 21.3R1, and all subsequent releases.