First published: Thu Oct 12 2023(Updated: )
An Improper Release of Memory Before Removing Last Reference vulnerability in Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows a local, low privileged attacker to cause an FPC crash, leading to Denial of Service (DoS). On all Junos MX Series with MPC1 - MPC9, LC480, LC2101, MX10003, and MX80, when Connectivity-Fault-Management (CFM) is enabled in a VPLS scenario, and a specific LDP related command is run, an FPC will crash and reboot. Continued execution of this specific LDP command can lead to sustained Denial of Service condition. This issue affects: Juniper Networks Junos OS on MX Series: * All versions prior to 20.4R3-S7; * 21.1 versions prior to 21.1R3-S5; * 21.2 versions prior to 21.2R3-S4; * 21.3 versions prior to 21.3R3-S4; * 21.4 versions prior to 21.4R3-S3; * 22.1 versions prior to 22.1R3-S1; * 22.2 versions prior to 22.2R2-S1, 22.2R3; * 22.3 versions prior to 22.3R1-S2, 22.3R2.
Credit: sirt@juniper.net
Affected Software | Affected Version | How to fix |
---|---|---|
Juniper Junos | <20.4 | |
Juniper Junos | =20.4 | |
Juniper Junos | =20.4-r1 | |
Juniper Junos | =20.4-r1-s1 | |
Juniper Junos | =20.4-r2 | |
Juniper Junos | =20.4-r2-s1 | |
Juniper Junos | =20.4-r2-s2 | |
Juniper Junos | =20.4-r3 | |
Juniper Junos | =20.4-r3-s1 | |
Juniper Junos | =20.4-r3-s2 | |
Juniper Junos | =20.4-r3-s3 | |
Juniper Junos | =20.4-r3-s4 | |
Juniper Junos | =20.4-r3-s5 | |
Juniper Junos | =20.4-r3-s6 | |
Juniper Junos | =21.1 | |
Juniper Junos | =21.1-r1 | |
Juniper Junos | =21.1-r1-s1 | |
Juniper Junos | =21.1-r2 | |
Juniper Junos | =21.1-r2-s1 | |
Juniper Junos | =21.1-r2-s2 | |
Juniper Junos | =21.1-r3 | |
Juniper Junos | =21.1-r3-s1 | |
Juniper Junos | =21.1-r3-s2 | |
Juniper Junos | =21.1-r3-s3 | |
Juniper Junos | =21.1-r3-s4 | |
Juniper Junos | =21.2 | |
Juniper Junos | =21.2-r1 | |
Juniper Junos | =21.2-r1-s1 | |
Juniper Junos | =21.2-r1-s2 | |
Juniper Junos | =21.2-r2 | |
Juniper Junos | =21.2-r2-s1 | |
Juniper Junos | =21.2-r2-s2 | |
Juniper Junos | =21.2-r3 | |
Juniper Junos | =21.2-r3-s1 | |
Juniper Junos | =21.2-r3-s2 | |
Juniper Junos | =21.2-r3-s3 | |
Juniper Junos | =21.3 | |
Juniper Junos | =21.3-r1 | |
Juniper Junos | =21.3-r1-s1 | |
Juniper Junos | =21.3-r1-s2 | |
Juniper Junos | =21.3-r2 | |
Juniper Junos | =21.3-r2-s1 | |
Juniper Junos | =21.3-r2-s2 | |
Juniper Junos | =21.3-r3 | |
Juniper Junos | =21.3-r3-s1 | |
Juniper Junos | =21.3-r3-s2 | |
Juniper Junos | =21.3-r3-s3 | |
Juniper Junos | =21.4 | |
Juniper Junos | =21.4-r1 | |
Juniper Junos | =21.4-r1-s1 | |
Juniper Junos | =21.4-r1-s2 | |
Juniper Junos | =21.4-r2 | |
Juniper Junos | =21.4-r2-s1 | |
Juniper Junos | =21.4-r2-s2 | |
Juniper Junos | =22.1-r1 | |
Juniper Junos | =22.1-r1-s1 | |
Juniper Junos | =22.1-r1-s2 | |
Juniper Junos | =22.1-r2 | |
Juniper Junos | =22.1-r2-s1 | |
Juniper Junos | =22.1-r2-s2 | |
Juniper Junos | =22.1-r3 | |
Juniper Junos | =22.2 | |
Juniper Junos | =22.2-r1 | |
Juniper Junos | =22.2-r1-s1 | |
Juniper Junos | =22.2-r1-s2 | |
Juniper Junos | =22.2-r2 | |
Juniper Junos | =22.3-r1 | |
Juniper Junos | =22.3-r1-s1 | |
Juniper Junos | =22.3-r1-s2 | |
Juniper Junos | =22.3-r2 | |
Juniper MX10003 | ||
Juniper MX10004 | ||
Juniper MX10008 | ||
Juniper MX2008 | ||
Juniper MX2010 | ||
Juniper MX2020 | ||
Juniper MX204 | ||
Juniper MX240 | ||
Juniper MX304 | ||
Juniper MX480 | ||
Juniper MX960 |
The following software releases have been updated to resolve this specific issue: Junos OS 20.4R3-S7, 21.1R3-S5, 21.2R3-S4, 21.3R3-S4, 21.4R3-S3, 22.1R3-S1, 22.2R2-S1, 22.2R3, 22.3R1-S2, 22.3R2, 22.4R1, and all subsequent releases.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-44193 has been categorized as a Denial of Service (DoS) vulnerability.
To mitigate CVE-2023-44193, upgrade Junos OS to a version greater than 20.4.
CVE-2023-44193 affects Juniper Networks Junos OS, specifically on all MX Series platforms utilizing MPC1 to MPC9.
An attacker exploiting CVE-2023-44193 can cause an FPC crash, resulting in network downtime.
Currently, there are no documented workarounds for CVE-2023-44193 other than upgrading the software.