First published: Fri Jan 12 2024(Updated: )
An Improper Handling of Syntactically Invalid Structure vulnerability in Object Flooding Protocol (OFP) service of Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). On all Junos OS Evolved platforms, when specific TCP packets are received on an open OFP port, the OFP crashes leading to a restart of Routine Engine (RE). Continuous receipt of these specific TCP packets will lead to a sustained Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS Evolved * All versions earlier than 21.2R3-S7-EVO; * 21.3 versions earlier than 21.3R3-S5-EVO ; * 21.4 versions earlier than 21.4R3-S5-EVO; * 22.1 versions earlier than 22.1R3-S4-EVO; * 22.2 versions earlier than 22.2R3-S3-EVO ; * 22.3 versions earlier than 22.3R3-EVO; * 22.4 versions earlier than 22.4R2-EVO, 22.4R3-EVO.
Credit: sirt@juniper.net
Affected Software | Affected Version | How to fix |
---|---|---|
Junos OS Evolved | <21.2 | |
Junos OS Evolved | =21.2 | |
Junos OS Evolved | =21.2-r1 | |
Junos OS Evolved | =21.2-r1-s1 | |
Junos OS Evolved | =21.2-r1-s2 | |
Junos OS Evolved | =21.2-r2 | |
Junos OS Evolved | =21.2-r2-s1 | |
Junos OS Evolved | =21.2-r2-s2 | |
Junos OS Evolved | =21.2-r3 | |
Junos OS Evolved | =21.2-r3-s1 | |
Junos OS Evolved | =21.2-r3-s2 | |
Junos OS Evolved | =21.2-r3-s3 | |
Junos OS Evolved | =21.2-r3-s4 | |
Junos OS Evolved | =21.2-r3-s5 | |
Junos OS Evolved | =21.2-r3-s6 | |
Junos OS Evolved | =21.3 | |
Junos OS Evolved | =21.3-r1 | |
Junos OS Evolved | =21.3-r1-s1 | |
Junos OS Evolved | =21.3-r2 | |
Junos OS Evolved | =21.3-r2-s1 | |
Junos OS Evolved | =21.3-r2-s2 | |
Junos OS Evolved | =21.3-r3 | |
Junos OS Evolved | =21.3-r3-s1 | |
Junos OS Evolved | =21.3-r3-s2 | |
Junos OS Evolved | =21.3-r3-s3 | |
Junos OS Evolved | =21.3-r3-s4 | |
Junos OS Evolved | =21.4 | |
Junos OS Evolved | =21.4-r1 | |
Junos OS Evolved | =21.4-r1-s1 | |
Junos OS Evolved | =21.4-r1-s2 | |
Junos OS Evolved | =21.4-r2 | |
Junos OS Evolved | =21.4-r2-s1 | |
Junos OS Evolved | =21.4-r2-s2 | |
Junos OS Evolved | =21.4-r3 | |
Junos OS Evolved | =21.4-r3-s1 | |
Junos OS Evolved | =21.4-r3-s2 | |
Junos OS Evolved | =21.4-r3-s3 | |
Junos OS Evolved | =21.4-r3-s4 | |
Junos OS Evolved | =22.1 | |
Junos OS Evolved | =22.1-r1 | |
Junos OS Evolved | =22.1-r1-s1 | |
Junos OS Evolved | =22.1-r1-s2 | |
Junos OS Evolved | =22.1-r2 | |
Junos OS Evolved | =22.1-r2-s1 | |
Junos OS Evolved | =22.1-r3 | |
Junos OS Evolved | =22.1-r3-s1 | |
Junos OS Evolved | =22.1-r3-s2 | |
Junos OS Evolved | =22.1-r3-s3 | |
Junos OS Evolved | =22.2 | |
Junos OS Evolved | =22.2-r1 | |
Junos OS Evolved | =22.2-r1-s1 | |
Junos OS Evolved | =22.2-r2 | |
Junos OS Evolved | =22.2-r2-s1 | |
Junos OS Evolved | =22.2-r2-s2 | |
Junos OS Evolved | =22.2-r3 | |
Junos OS Evolved | =22.2-r3-s1 | |
Junos OS Evolved | =22.2-r3-s2 | |
Junos OS Evolved | =22.3 | |
Junos OS Evolved | =22.3-r1 | |
Junos OS Evolved | =22.3-r1-s1 | |
Junos OS Evolved | =22.3-r1-s2 | |
Junos OS Evolved | =22.3-r2 | |
Junos OS Evolved | =22.3-r2-s1 | |
Junos OS Evolved | =22.3-r2-s2 | |
Junos OS Evolved | =22.4 | |
Junos OS Evolved | =22.4-r1 | |
Junos OS Evolved | =22.4-r1-s1 | |
Junos OS Evolved | =22.4-r1-s2 |
The following software releases have been updated to resolve this specific issue: Junos OS Evolved: 21.2R3-S7-EVO, 21.3R3-S5-EVO, 21.4R3-S5-EVO, 22.1R3-S4-EVO, 22.2R3-S3-EVO, 22.3R3-EVO, 22.4R2-EVO, 22.4R3-EVO, 23.2R1-EVO, and all subsequent releases.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-21612 has been classified as a High severity vulnerability due to its potential to cause a Denial of Service.
To address CVE-2024-21612, upgrade to Junos OS Evolved version 21.2 or later, as per the vendor's recommendations.
An unauthenticated, network-based attacker can exploit CVE-2024-21612 to induce a Denial of Service on affected systems.
CVE-2024-21612 affects all Junos OS Evolved platforms prior to version 21.2.
Currently, there are no specific workarounds available for CVE-2024-21612, and upgrading is recommended for mitigation.