medium
5.9
CWE
19
Advisory Published
Updated

CVE-2021-0263: Junos OS: PTX Series: Denial of Service in packet processing due to heavy route churn when J-Flow sampling is enabled

First published: Thu Apr 22 2021(Updated: )

A Data Processing vulnerability in the Multi-Service process (multi-svcs) on the FPC of Juniper Networks Junos OS on the PTX Series routers may lead to the process becoming unresponsive, ultimately affecting traffic forwarding, allowing an attacker to cause a Denial of Service (DoS) condition . The Multi-Service Process running on the FPC is responsible for handling sampling-related operations when a J-Flow configuration is activated. This can occur during periods of heavy route churn, causing the Multi-Service Process to stop processing updates, without consuming any further updates from kernel. This back pressure towards the kernel affects further dynamic updates from other processes in the system, including RPD, causing a KRT-STUCK condition and traffic forwarding issues. An administrator can monitor the following command to check if there is the KRT queue is stuck: user@device > show krt state ... Number of async queue entries: 65007 <--- this value keep on increasing. The following logs/alarms will be observed when this condition exists: user@junos> show chassis alarms 2 alarms currently active Alarm time Class Description 2020-10-11 04:33:45 PDT Minor Potential slow peers are: MSP(FPC1-PIC0) MSP(FPC3-PIC0) MSP(FPC4-PIC0) Logs: Oct 11 04:33:44.672 2020 test /kernel: rts_peer_cp_recv_timeout : Bit set for msp8 as it is stuck Oct 11 04:35:56.000 2020 test-lab fpc4 user.err gldfpc-multi-svcs.elf: Error in parsing composite nexthop Oct 11 04:35:56.000 2020 test-lab fpc4 user.err gldfpc-multi-svcs.elf: composite nexthop parsing error Oct 11 04:43:05 2020 test /kernel: rt_pfe_veto: Possible slowest client is msp38. States processed - 65865741. States to be processed - 0 Oct 11 04:55:55 2020 test /kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (8311787520) Current delayed unref = (60000), Current unique delayed unref = (10896), Max delayed unref on this platform = (40000) Current delayed weight unref = (71426) Max delayed weight unref on this platform= (400000) curproc = rpd Oct 11 04:56:00 2020 test /kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2 This issue only affects PTX Series devices. No other products or platforms are affected by this vulnerability. This issue affects Juniper Networks Junos OS on PTX Series: 18.2 versions prior to 18.2R3-S7; 18.3 versions prior to 18.3R3-S4; 18.4 versions prior to 18.4R2-S8, 18.4R3-S7; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R3-S1; 19.3 versions prior to 19.3R3-S1; 19.4 versions prior to 19.4R2-S4, 19.4R3-S1; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R2; 20.3 versions prior to 20.3R1-S2, 20.3R2. This issue does not affect Juniper Networks Junos OS versions prior to 18.2R1.

Credit: sirt@juniper.net

Affected SoftwareAffected VersionHow to fix
Juniper JUNOS=18.2
Juniper JUNOS=18.2-r1
Juniper JUNOS=18.2-r1
Juniper JUNOS=18.2-r1-s2
Juniper JUNOS=18.2-r1-s3
Juniper JUNOS=18.2-r1-s4
Juniper JUNOS=18.2-r1-s5
Juniper JUNOS=18.2-r2
Juniper JUNOS=18.2-r2-s1
Juniper JUNOS=18.2-r2-s2
Juniper JUNOS=18.2-r2-s3
Juniper JUNOS=18.2-r2-s4
Juniper JUNOS=18.2-r2-s5
Juniper JUNOS=18.2-r2-s6
Juniper JUNOS=18.2-r2-s7
Juniper JUNOS=18.2-r3
Juniper JUNOS=18.2-r3-s1
Juniper JUNOS=18.2-r3-s2
Juniper JUNOS=18.2-r3-s3
Juniper JUNOS=18.2-r3-s4
Juniper JUNOS=18.2-r3-s5
Juniper JUNOS=18.2-r3-s6
Juniper JUNOS=18.3
Juniper JUNOS=18.3-r1
Juniper JUNOS=18.3-r1-s1
Juniper JUNOS=18.3-r1-s2
Juniper JUNOS=18.3-r1-s3
Juniper JUNOS=18.3-r1-s4
Juniper JUNOS=18.3-r1-s5
Juniper JUNOS=18.3-r1-s6
Juniper JUNOS=18.3-r2
Juniper JUNOS=18.3-r2-s1
Juniper JUNOS=18.3-r2-s2
Juniper JUNOS=18.3-r2-s3
Juniper JUNOS=18.3-r2-s4
Juniper JUNOS=18.3-r3
Juniper JUNOS=18.3-r3-s1
Juniper JUNOS=18.3-r3-s2
Juniper JUNOS=18.3-r3-s3
Juniper JUNOS=18.4
Juniper JUNOS=18.4-r1
Juniper JUNOS=18.4-r1-s1
Juniper JUNOS=18.4-r1-s2
Juniper JUNOS=18.4-r1-s3
Juniper JUNOS=18.4-r1-s4
Juniper JUNOS=18.4-r1-s5
Juniper JUNOS=18.4-r1-s6
Juniper JUNOS=18.4-r1-s7
Juniper JUNOS=18.4-r2
Juniper JUNOS=18.4-r2-s1
Juniper JUNOS=18.4-r2-s2
Juniper JUNOS=18.4-r2-s3
Juniper JUNOS=18.4-r2-s4
Juniper JUNOS=18.4-r2-s5
Juniper JUNOS=18.4-r2-s6
Juniper JUNOS=18.4-r2-s7
Juniper JUNOS=18.4-r3
Juniper JUNOS=18.4-r3-s1
Juniper JUNOS=18.4-r3-s2
Juniper JUNOS=18.4-r3-s3
Juniper JUNOS=18.4-r3-s4
Juniper JUNOS=18.4-r3-s5
Juniper JUNOS=18.4-r3-s6
Juniper JUNOS=19.1
Juniper JUNOS=19.1-r1
Juniper JUNOS=19.1-r1-s1
Juniper JUNOS=19.1-r1-s2
Juniper JUNOS=19.1-r1-s3
Juniper JUNOS=19.1-r1-s4
Juniper JUNOS=19.1-r1-s5
Juniper JUNOS=19.1-r2
Juniper JUNOS=19.1-r2-s1
Juniper JUNOS=19.1-r3
Juniper JUNOS=19.1-r3-s1
Juniper JUNOS=19.1-r3-s2
Juniper JUNOS=19.1-r3-s3
Juniper JUNOS=19.2
Juniper JUNOS=19.2-r1
Juniper JUNOS=19.2-r1-s1
Juniper JUNOS=19.2-r1-s2
Juniper JUNOS=19.2-r1-s3
Juniper JUNOS=19.2-r1-s4
Juniper JUNOS=19.2-r1-s5
Juniper JUNOS=19.2-r2
Juniper JUNOS=19.2-r2-s1
Juniper JUNOS=19.2-r3
Juniper JUNOS=19.3
Juniper JUNOS=19.3-r1
Juniper JUNOS=19.3-r1-s1
Juniper JUNOS=19.3-r2
Juniper JUNOS=19.3-r2-s1
Juniper JUNOS=19.3-r2-s2
Juniper JUNOS=19.3-r2-s3
Juniper JUNOS=19.3-r2-s4
Juniper JUNOS=19.3-r2-s5
Juniper JUNOS=19.3-r3
Juniper JUNOS=19.4-r1
Juniper JUNOS=19.4-r1-s1
Juniper JUNOS=19.4-r1-s2
Juniper JUNOS=19.4-r2
Juniper JUNOS=19.4-r2-s1
Juniper JUNOS=19.4-r2-s2
Juniper JUNOS=19.4-r2-s3
Juniper JUNOS=19.4-r3
Juniper JUNOS=20.1-r1
Juniper JUNOS=20.1-r1-s1
Juniper JUNOS=20.1-r1-s2
Juniper JUNOS=20.1-r1-s3
Juniper JUNOS=20.1-r1-s4
Juniper JUNOS=20.2-r1
Juniper JUNOS=20.2-r1-s1
Juniper JUNOS=20.2-r1-s2
Juniper JUNOS=20.2-r1-s3
Juniper JUNOS=20.3-r1
Juniper JUNOS=20.3-r1-s1
Juniper Ptx1000
Juniper Ptx10001-36mr
Juniper Ptx10002
Juniper Ptx10003
Juniper Ptx10004
Juniper Ptx10008
Juniper Ptx10016
Juniper Ptx3000
Juniper Ptx5000

Remedy

The following software releases have been updated to resolve this specific issue: Junos OS 18.2R3-S7, 18.3R3-S4, 18.4R2-S8, 18.4R3-S7, 19.1R3-S4, 19.2R3-S1, 19.3R3-S1, 19.4R2-S4, 19.4R3-S1, 20.1R2, 20.2R2, 20.3R1-S2, 20.3R2, 20.4R1, and all subsequent releases.

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203