high
7.5
CWE
20
Advisory Published
Updated

CVE-2020-1679: Junos OS: PTX/QFX Series: Kernel Routing Table (KRT) queue stuck after packet sampling a malformed packet when the tunnel-observation mpls-over-udp configuration is enabled.

First published: Fri Oct 16 2020(Updated: )

On Juniper Networks PTX and QFX Series devices with packet sampling configured using tunnel-observation mpls-over-udp, sampling of a malformed packet can cause the Kernel Routing Table (KRT) queue to become stuck. KRT is the module within the Routing Process Daemon (RPD) that synchronized the routing tables with the forwarding tables in the kernel. This table is then synchronized to the Packet Forwarding Engine (PFE) via the KRT queue. Thus, when KRT queue become stuck, it can lead to unexpected packet 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. When this issue occurs, the following message might appear in the /var/log/messages: DATE DEVICE kernel: %KERN-3: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2 err 55, rtsm_id 5:-1, msg type 2 DATE DEVICE kernel: %KERN-3: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for M_RTNEXTHOP type = (7297134592) Current delayed unref = (60000), Current unique delayed unref = (18420), Max delayed unref on this platform = (40000) Current delayed weight unref = (60000) Max delayed weight unref on this platform= (400000) curproc = rpd This issue affects Juniper Networks Junos OS on PTX/QFX Series: 17.2X75 versions prior to 17.2X75-D105; 18.1 versions prior to 18.1R3-S11; 18.2 versions prior to 18.2R3-S5; 18.2X75 versions prior to 18.2X75-D420, 18.2X75-D53, 18.2X75-D65; 18.3 versions prior to 18.3R2-S4, 18.3R3-S3; 18.4 versions prior to 18.4R1-S7, 18.4R2-S5, 18.4R3-S4; 19.1 versions prior to 19.1R2-S2, 19.1R3-S2; 19.2 versions prior to 19.2R1-S5, 19.2R3; 19.3 versions prior to 19.3R2-S3, 19.3R3; 19.4 versions prior to 19.4R1-S2, 19.4R2-S1, 19.4R3; 20.1 versions prior to 20.1R1-S2, 20.1R2. This issue does not affect Juniper Networks Junos OS prior to 18.1R1.

Credit: sirt@juniper.net

Affected SoftwareAffected VersionHow to fix
Juniper Junos=17.2x75
Juniper Junos=17.2x75
Juniper Junos=17.2x75-d102
Juniper Junos=17.2x75-d50
Juniper Junos=17.2x75-d70
Juniper Junos=17.2x75-d92
Juniper Junos=18.1
Juniper Junos=18.1-r1
Juniper Junos=18.1-r2
Juniper Junos=18.1-r2-s1
Juniper Junos=18.1-r2-s2
Juniper Junos=18.1-r2-s4
Juniper Junos=18.1-r3
Juniper Junos=18.1-r3-s1
Juniper Junos=18.1-r3-s10
Juniper Junos=18.1-r3-s2
Juniper Junos=18.1-r3-s3
Juniper Junos=18.1-r3-s4
Juniper Junos=18.1-r3-s6
Juniper Junos=18.1-r3-s7
Juniper Junos=18.1-r3-s8
Juniper Junos=18.1-r3-s9
Juniper Junos=18.2
Juniper Junos=18.2-r1
Juniper Junos=18.2-r1
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-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.2x75
Juniper Junos=18.2x75-d12
Juniper Junos=18.2x75-d20
Juniper Junos=18.2x75-d30
Juniper Junos=18.2x75-d40
Juniper Junos=18.2x75-d411
Juniper Junos=18.2x75-d51
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-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-r3
Juniper Junos=18.3-r3-s1
Juniper Junos=18.3-r3-s2
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-s5
Juniper Junos=18.4-r1-s6
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-r3
Juniper Junos=18.4-r3-s1
Juniper Junos=18.4-r3-s2
Juniper Junos=18.4-r3-s3
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-r2
Juniper Junos=19.1-r2-s1
Juniper Junos=19.1-r3
Juniper Junos=19.1-r3-s1
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.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.4-r1
Juniper Junos=19.4-r1-s1
Juniper Junos=19.4-r2
Juniper Junos=20.1-r1
Juniper Junos=20.1-r1-s1
Juniper PTX1000
Juniper PTX10001-36MR
Juniper PTX10016
Juniper PTX10002
Juniper PTX10003 80C
Juniper PTX10004
Juniper PTX10008
Juniper PTX3000
Juniper PTX5000
Juniper QFX10002-60C
Juniper QFX10008
Juniper QFX10016
Juniper QFX5100
Juniper QFX5110
Juniper QFX5120
Juniper QFX5130
Juniper QFX5200-48Y
Juniper QFX5210-64C
Juniper QFX5220

Remedy

The following software releases have been updated to resolve this specific issue: Junos OS 17.2X75-D105, 18.1R3-S11, 18.2R3-S5, 18.2X75-D420, 18.2X75-D53, 18.2X75-D65, 18.3R2-S4, 18.3R3-S3, 18.4R1-S7, 18.4R2-S5, 18.4R3-S4, 19.1R2-S2, 19.1R3-S2, 19.2R1-S5, 19.2R3, 19.3R2-S3, 19.3R3, 19.4R1-S2, 19.4R2-S1, 19.4R3, 20.1R1-S2, 20.1R2, 20.2R1, 20.3X75-D10, 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

Frequently Asked Questions

  • What is the severity of CVE-2020-1679?

    CVE-2020-1679 is classified as a moderate severity vulnerability due to its potential impact on routing functionality.

  • How do I fix CVE-2020-1679?

    To remediate CVE-2020-1679, it is recommended to upgrade the affected Juniper Networks devices to a patched version of the Junos operating system.

  • What devices are affected by CVE-2020-1679?

    CVE-2020-1679 affects Juniper Networks PTX and QFX Series devices configured with packet sampling using tunnel-observation mpls-over-udp.

  • What kind of issues does CVE-2020-1679 cause?

    CVE-2020-1679 can cause the Kernel Routing Table queue to become stuck when handling malformed packets.

  • Are there any workarounds for CVE-2020-1679?

    Currently, there are no specific workarounds documented for CVE-2020-1679 other than upgrading devices to the latest firmware.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203