CVSS: v3.1: 6.5 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)CVSS: v4.0: 7.1 (CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/R:U)
An Improper Handling of Exceptional Conditions vulnerability in packet processing of Juniper Networks Junos OS on MX Series with MPC10/MPC11/LC9600 line cards, EX9200 with EX9200-15C lines cards, MX304 devices, and Juniper Networks Junos OS Evolved on PTX Series, allows an attacker sending malformed DHCP packets to cause ingress packet processing to stop, leading to a Denial of Service (DoS). Continued receipt and processing of these packets will create a sustained Denial of Service (DoS) condition.This issue only occurs if DHCP snooping is enabled. See configuration below.This issue can be detected using following commands. Their output will display the interface status going down:user@device>show interfaces <if--x/x/x>user@device>show log messages | match <if--x/x/x>user@device>show log messages ==> will display the "[Error] Wedge-Detect : Host Loopback Wedge Detected: PFE: no," logs.
This issue affects:Junos OS on MX Series with MPC10/MPC11/LC9600 line cards, EX9200 with EX9200-15C line cards, and MX304:
Junos OS Evolved on PTX Series:
Junos OS Evolved releases prior to 19.3R1-EVO are unaffected by this vulnerability
DHCP snooping is enabled when the following options are configured:[forwarding-options dhcp-relay][system services dhcp-local-server]
Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
This issue was seen during production usage.
The following software releases have been updated to resolve this specific issue:Junos OS: 21.2R3-S7, 21.4R3-S6, 22.2R3-S3, 22.4R3, 23.2R2, 23.4R2, 24.2R1, and all subsequent releases.Junos OS Evolved: 21.2R3-S8-EVO, 21.4R3-S7-EVO, 22.1R3-S6-EVO, 22.2R3-S5-EVO*, 22.3R3-S3-EVO, 22.4R3-S1-EVO, 23.2R2-S2-EVO, 23.4R2-EVO, 24.2R1-EVO, and all subsequent releases.*Future release
This issue is being tracked as 1772092 which is visible on the Customer Support website.
Note: Juniper SIRT's policy is not to evaluate releases which are beyond End of Engineering (EOE) or End of Life (EOL).
There are no known workarounds for this issue.
2024-10-09: Initial Publication