medium
6.5
Advisory Published
Updated

CVE-2017-10611: Junos: EX Series PFE and MX MPC7E/8E/9E PFE crash when fetching interface stats with 'extended-statistics' enabled

First published: Fri Oct 13 2017(Updated: )

If extended statistics are enabled via 'set chassis extended-statistics', when executing any operation that fetches interface statistics, including but not limited to SNMP GET requests, the pfem process or the FPC may crash and restart. Repeated crashes of PFE processing can result in an extended denial of service condition. This issue only affects the following platforms: (1) EX2200, EX3300, XRE200 (2) MX Series routers with MPC7E/8E/9E PFEs installed, and only if 'extended-statistics' are enabled under the [edit chassis] configuration. Affected releases are Juniper Networks Junos OS 14.1 prior to 14.1R8-S5, 14.1R9 on MX Series; 14.1X53 prior to 14.1X53-D46, 14.1X53-D50 on EX2200, EX3300, XRE200; 14.2 prior to 14.2R7-S9, 14.2R8 on MX Series; 15.1 prior to 15.1F5-S8, 15.1F6-S8, 15.1R5-S3, 15.1R6 on MX Series; 16.1 prior to 16.1R4-S5, 16.1R5, 16.1R6 on MX Series; 16.1X65 prior to 16.1X65-D45 on EX2200, EX3300, XRE200; 16.2 prior to 16.2R2-S1, 16.2R3 on MX Series; 17.1 prior to 17.1R2-S2, 17.1R3 on MX Series; 17.2 prior to 17.2R1-S3, 17.2R2 on MX Series; 17.2X75 prior to 17.2X75-D50 on MX Series; 17.3 prior to 17.3R1-S1, 17.3R2 on MX Series. No other Juniper Networks products or platforms are affected by this issue.

Credit: sirt@juniper.net

Affected SoftwareAffected VersionHow to fix
Juniper Junos=14.1
Juniper Junos=14.1-r1
Juniper Junos=14.1-r2
Juniper Junos=14.1-r3
Juniper Junos=14.1-r4
Juniper Junos=14.1-r5
Juniper Junos=14.1-r6
Juniper Junos=14.1-r7
Juniper Junos=14.1-r8
Juniper Junos=14.1-r9
Juniper MX10
Juniper MX104
Juniper MX2010
Juniper MX2020
Juniper MX240
Juniper MX40
Juniper MX480
Juniper MX5
Juniper MX80
Juniper MX960
Juniper vMX
Juniper Junos=14.1x53
Juniper Junos=14.1x53-d10
Juniper Junos=14.1x53-d15
Juniper Junos=14.1x53-d16
Juniper Junos=14.1x53-d25
Juniper Junos=14.1x53-d26
Juniper Junos=14.1x53-d27
Juniper Junos=14.1x53-d30
Juniper Junos=14.1x53-d35
Juniper Junos=14.1x53-d40
Juniper Junos=14.1x53-d45
Juniper Junos=14.1x53-d50
Juniper EX2200
Juniper EX3300
Juniper xre200
Juniper Junos=14.2
Juniper Junos=14.2-r1
Juniper Junos=14.2-r2
Juniper Junos=14.2-r3
Juniper Junos=14.2-r4
Juniper Junos=14.2-r5
Juniper Junos=14.2-r6
Juniper Junos=14.2-r7
Juniper Junos=14.2-r8
Juniper Junos=15.1-f1
Juniper Junos=15.1-f2
Juniper Junos=15.1-f2-s1
Juniper Junos=15.1-f2-s2
Juniper Junos=15.1-f2-s3
Juniper Junos=15.1-f2-s4
Juniper Junos=15.1-f3
Juniper Junos=15.1-f4
Juniper Junos=15.1-f5
Juniper Junos=15.1-f6-s8
Juniper Junos=15.1-r1
Juniper Junos=15.1-r2
Juniper Junos=15.1-r3
Juniper Junos=15.1-r4
Juniper Junos=15.1-r5
Juniper Junos=15.1-r5-s3
Juniper Junos=15.1-r6
Juniper Junos=16.1-r1
Juniper Junos=16.1-r2
Juniper Junos=16.1-r3
Juniper Junos=16.1-r4
Juniper Junos=16.1-r5
Juniper Junos=16.1-r6
Juniper Junos=16.1x65
Juniper Junos=16.1x65-d30
Juniper Junos=16.1x65-d35
Juniper Junos=16.1x65-d40
Juniper Junos=16.2
Juniper Junos=16.2-r1
Juniper Junos=16.2-r2
Juniper Junos=16.2-r3
Juniper Junos=17.1
Juniper Junos=17.1-r1
Juniper Junos=17.1-r2
Juniper Junos=17.1-r3
Juniper Junos=17.2
Juniper Junos=17.2-r1
Juniper Junos=17.2-r2
Juniper Junos=17.2x75
Juniper Junos=17.3-r1

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-2017-10611?

    CVE-2017-10611 has a high severity rating due to the potential for repeated crashes of the PFE process, disrupting network operations.

  • How do I fix CVE-2017-10611?

    To fix CVE-2017-10611, disable the extended statistics feature if currently enabled on affected Juniper JUNOS versions.

  • Which versions of Juniper JUNOS are affected by CVE-2017-10611?

    CVE-2017-10611 affects Juniper JUNOS versions 14.1 and several 14.2 revisions.

  • What are the potential consequences of CVE-2017-10611?

    The consequences of CVE-2017-10611 include potential network downtime and instability due to crashes of the PFE process.

  • Is there a workaround for CVE-2017-10611 until a patch is available?

    A temporary workaround for CVE-2017-10611 is to refrain from executing any operations that fetch interface statistics when extended statistics are enabled.

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