# What is CVE-2017-10611? > CVE-2017-10611 is a medium-severity flaw (CVSS 5.9) in Junos from Juniper, published on 13 October 2017. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.9%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2017-10611 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Precursor Intelligence risk score:** 23 out of 100 (Low); action: Monitor. Kept up to date as the evidence changes. - **Severity:** Medium (CVSS 5.9 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 0.9% (latest exploit-likelihood forecast) - **Published:** 13 October 2017 - **Record last updated:** 20 April 2025 - **Main product:** Junos from Juniper - **Affected products:** 15 ## What is CVE-2017-10611? In plain terms It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline. ### The official description 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. ### What kind of flaw is it? - Unknown: Unknown ### How an attack on it works - Where an attacker can be: Anywhere on the internet - How hard it is to pull off: Hard: conditions must line up - Login needed first: No login needed - Does someone have to click: No, nobody has to do anything - What an attacker gets: Can take it offline Severity vector: `CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H` ## Is CVE-2017-10611 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.9%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 0.9%, 0.9%, 0.9%, 0.9%, 0.9%, 0.9%, 0.9%. ### Timeline - 13 October 2017: Published - 20 April 2025: Record last updated ### How Precursor Intelligence ranks it CVE-2017-10611 scores **23 out of 100 (Low)**, with the action "Monitor". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2017-10611? The published record lists 15 products. - [Junos](https://www.precursorintelligence.com/product/juniper/junos) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Operating system): 14.1, 14.1-r1, 14.1-r2, 14.1-r3, 14.1-r4, 14.1-r5, 14.1-r6, 14.1-r7, 14.1-r8, 14.1-r9, 14.1x53, 14.1x53-d10, 14.1x53-d15, 14.1x53-d16, 14.1x53-d25, 14.1x53-d26, 14.1x53-d27, 14.1x53-d30, 14.1x53-d35, 14.1x53-d40, 14.1x53-d45, 14.1x53-d50, 14.2, 14.2-r1, 14.2-r2, 14.2-r3, 14.2-r4, 14.2-r5, 14.2-r6, 14.2-r7, 14.2-r8, 15.1-f1, 15.1-f2, 15.1-f2-s1, 15.1-f2-s2, 15.1-f2-s3, 15.1-f2-s4, 15.1-f3, 15.1-f4, 15.1-f5 and 31 more - [Ex2200](https://www.precursorintelligence.com/product/juniper/ex2200) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Ex3300](https://www.precursorintelligence.com/product/juniper/ex3300) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Mx10](https://www.precursorintelligence.com/product/juniper/mx10) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Mx104](https://www.precursorintelligence.com/product/juniper/mx104) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Mx2010](https://www.precursorintelligence.com/product/juniper/mx2010) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Mx2020](https://www.precursorintelligence.com/product/juniper/mx2020) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Mx240](https://www.precursorintelligence.com/product/juniper/mx240) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Mx40](https://www.precursorintelligence.com/product/juniper/mx40) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Mx480](https://www.precursorintelligence.com/product/juniper/mx480) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Mx5](https://www.precursorintelligence.com/product/juniper/mx5) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Mx80](https://www.precursorintelligence.com/product/juniper/mx80) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Mx960](https://www.precursorintelligence.com/product/juniper/mx960) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Vmx](https://www.precursorintelligence.com/product/juniper/vmx) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Xre200](https://www.precursorintelligence.com/product/juniper/xre200) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified ## How do I fix CVE-2017-10611? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [kb.juniper.net](https://kb.juniper.net/JSA10814) (Vendor advisory) ## Questions ### What is CVE-2017-10611? CVE-2017-10611 is a medium-severity flaw in Junos from Juniper, published on 13 October 2017. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline. ### How serious is CVE-2017-10611? It scores 5.9 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2017-10611 is 23 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2017-10611 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.9%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2017-10611 affect? For Junos from Juniper: 14.1, 14.1-r1, 14.1-r2, 14.1-r3, 14.1-r4, 14.1-r5 and 65 more. The record lists 15 products in all, each with its versions, under "Who is affected" on this page. ### How do I fix CVE-2017-10611? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2017-10611 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact