CVE-2022-22153: SRX Series and MX Series with SPC3: A high percentage of fragments might lead to high latency or packet drops
An Insufficient Algorithmic Complexity combined with an Allocation of Resources Without Limits or Throttling vulnerability in the flow processing daemon (flowd) of Juniper Networks Junos OS on SRX Series and MX Series with SPC3 allows an unauthenticated network attacker to cause latency in transit packet processing and even packet loss. If transit traffic includes a significant percentage (> 5%) of fragmented packets which need to be reassembled, high latency or packet drops might be observed. This issue affects Juniper Networks Junos OS on SRX Series, MX Series with SPC3: All versions prior to 18.2R3; 18.3 versions prior to 18.3R3; 18.4 versions prior to 18.4R2-S9, 18.4R3; 19.1 versions prior to 19.1R2; 19.2 versions prior to 19.2R1-S1, 19.2R2.
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2022-22153?
CVE-2022-22153 is rated as a high-severity vulnerability in the Junos OS.
How do I fix CVE-2022-22153?
To fix CVE-2022-22153, users are advised to upgrade to the latest version of Junos OS that contains the security fix.
What systems are affected by CVE-2022-22153?
CVE-2022-22153 affects Juniper Networks' SRX Series and MX Series running specific versions of Junos OS.
What type of attacks can exploit CVE-2022-22153?
CVE-2022-22153 can be exploited by an unauthenticated network attacker to cause latency or denial of service.
Is there a workaround for CVE-2022-22153?
There is no specific workaround for CVE-2022-22153; upgrading the software is the recommended approach.