synced 5 MIN AGO
01 Record

CVE-2022-22153

SRX Series and MX Series with SPC3: A high percentage of fragments might lead to high latency or packet drops

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

SRX Series and MX Series with SPC3: A high percentage of fragments might lead to high latency or packet drops

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:20Z4 YR AGO
Last updated
2024-09-17 01:50Z2 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-407Inefficient Algorithmic ComplexityClass
  • CWE-770Allocation of Resources Without Limits or ThrottlingBase
Data version
5.1
Document digest
cbd2da75a2ca47c979cfee03ebade0751d74b0ebcaee6c8abb6a3831639b8b30

05 Affected products

VendorProductVersionsPlatforms
Juniper NetworksJunos OS< 18.2R3, 18.3 to < 18.3R3, 18.4 to < 18.4R2-S9, 18.4R3, 19.1 to < 19.1R2, 19.2 to < 19.2R1-S1, 19.2R2SRX Series, MX Series with SPC3

06 References

07 Remediation

The following software releases have been updated to resolve this specific issue: 18.2R3, 18.3R3, 18.4R2-S9, 18.4R3, 19.1R2, 19.2R1-S1, 19.2R2, 19.3R1, and all subsequent releases.