Skip to main content
← All vulnerabilities
CVE-2024-21600

Junos OS: PTX Series: In an FTI scenario MPLS packets hitting reject next-hop will cause a host path wedge condition

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 20.4R3-S8, 21.1R3-S4, 21.2R3-S6, 21.3R3-S3, 21.4R3-S5
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

An Improper Neutralization of Equivalent Special Elements vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on PTX Series allows a unauthenticated, adjacent attacker to cause a Denial of Service (DoS). When MPLS packets are meant to be sent to a flexible tunnel interface (FTI) and if the FTI tunnel is down, these will hit the reject NH, due to which the packets get sent to the CPU and cause a host path wedge condition. This will cause the FPC to hang and requires a manual restart to recover. Please note that this issue specifically affects PTX1000, PTX3000, PTX5000 with FPC3, PTX10002-60C, and PTX10008/16 with LC110x. Other PTX Series devices and Line Cards (LC) are not affected. The following log message can be seen when the issue occurs: Cmerror Op Set: Host Loopback: HOST LOOPBACK WEDGE DETECTED IN PATH ID <id> (URI: /fpc/<fpc>/pfe/<pfe>/cm/<cm>/Host_Loopback/<cm>/HOST_LOOPBACK_MAKE_CMERROR_ID[<id>]) This issue affects Juniper Networks Junos OS: • All versions earlier than 20.4R3-S8; • 21.1 versions earlier than 21.1R3-S4; • 21.2 versions earlier than 21.2R3-S6; • 21.3 versions earlier than 21.3R3-S3; • 21.4 versions earlier than 21.4R3-S5; • 22.1 versions earlier than 22.1R2-S2, 22.1R3; • 22.2 versions earlier than 22.2R2-S1, 22.2R3.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • Juniper Networks Junos OS

    fixed in 20.4R3-S8; From 21.1 · fixed in 21.1R3-S4; From 21.2 · fixed in 21.2R3-S6; From 21.3 · fixed in 21.3R3-S3; From 21.4 · fixed in 21.4R3-S5

References 2

supportportal.juniper.net

first.org