An Improper Validation of Syntactic Correctness of Input vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on MX Series with MPC10/11 or LC9600, MX304, and Junos OS Evolved on ACX Series and PTX Series allows an unauthenticated, network based attacker to cause a Denial-of-Service (DoS).This issue can occur in two scenarios:1. If a device, which is configured with SFLOW and ECMP, receives specific valid transit traffic, which is subject to sampling, the packetio process crashes, which in turn leads to an evo-aftman crash and causes the FPC to stop working until it is restarted. (This scenario is only applicable to PTX but not to ACX or MX.)2. If a device receives a malformed CFM packet on an interface configured with CFM, the packetio process crashes, which in turn leads to an evo-aftman crash and causes the FPC to stop working until it is restarted.
Please note that the CVSS score is for the formally more severe issue 1.
The CVSS score for scenario 2. is: 6.5 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
This issue affects Junos OS:
Junos OS Evolved:
To be exposed to this issue at least one of CFM or sampling needs to be configured:1. CFM:
[ protocols oam ethernet connectivity-fault-management maintenance-domain <md_name> maintenance-association <ma_name> mep <number> interface <interface> ]
or
[ protocols oam ethernet connectivity-fault-management maintenance-domain <md_name> interface <interface> / vlan <vlan> ]
2. ECMP, sampling
[ protocols sflow interfaces <interface> ]
This issue was seen during production usage.
The following software releases have been updated to resolve this specific issue:Junos OS: 21.2R3-S4, 21.4R2, 22.2R2-S1, 22.2R3, 22.3R1, and all subsequent releases.Junos OS Evolved: 21.2R3-S8-EVO, 21.4R2-EVO, 22.2R1-EVO, and all subsequent releases.
This issue is being tracked as 1654270 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).
Exposure to this issue can be avoided by disabling the affected features:
1. disable CFM by removing or deactivating:
[ protocols oam ethernet connectivity-fault-management ]
2. disable sampling by removing or deactivating the respective interfaces:
[ protocols sflow interfaces <interfacce> ]
2024-07-10: Initial Publication 2024-09-13: Minor formatting change to CVSS field