# What is CVE-2022-22202? > CVE-2022-22202 is a medium-severity flaw (CVSS 6.5) in Junos from Juniper, published on 20 July 2022. 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.5%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2022-22202 ## 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:** 43 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes. - **Severity:** Medium (CVSS 6.5 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.5% (latest exploit-likelihood forecast) - **Published:** 20 July 2022 - **Record last updated:** 27 July 2022 - **Main product:** Junos from Juniper - **Affected products:** 7 ## What is CVE-2022-22202? In plain terms An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can take it offline. ### The official description An Improper Handling of Exceptional Conditions vulnerability on specific PTX Series devices, including the PTX1000, PTX3000 (NextGen), PTX5000, PTX10002-60C, PTX10008, and PTX10016 Series, in Juniper Networks Junos OS allows an unauthenticated MPLS-based attacker to cause a Denial of Service (DoS) by triggering the dcpfe process to crash and FPC to restart. On affected PTX Series devices, processing specific MPLS packets received on an interface with multiple units configured may cause FPC to restart unexpectedly. Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition. This issue only affects PTX Series devices utilizing specific FPCs found on PTX1000, PTX3000 (NextGen), PTX5000, PTX10002-60C, PTX10008, and PTX10016 Series devices, only if multiple units are configured on the ingress interface, and at least one unit has 'family mpls' *not* configured. See the configuration sample below for more information. No other platforms are affected by this vulnerability. This issue affects: Juniper Networks Junos OS on PTX Series: All versions prior to 19.1R3-S9; 19.2 versions prior to 19.2R3-S6; 19.3 versions prior to 19.3R3-S6; 19.4 versions prior to 19.4R3-S8; 20.1 versions prior to 20.1R3-S4; 20.2 versions prior to 20.2R3-S5; 20.3 versions prior to 20.3R3-S4; 20.4 versions prior to 20.4R3-S4; 21.1 versions prior to 21.1R3-S2; 21.2 versions prior to 21.2R3-S1; 21.3 versions prior to 21.3R3; 21.4 versions prior to 21.4R2; 22.1 versions prior to 22.1R2. ### What kind of flaw is it? - CWE-755: Improper Handling of Exceptional Conditions ### How an attack on it works - Where an attacker can be: On the same local network - How hard it is to pull off: Easy: no special conditions - 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.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` ## Is CVE-2022-22202 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.5%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 0.5%, 0.5%, 0.5%, 0.5%, 0.5%, 0.5%, 0.5%. ### Timeline - 20 July 2022: Published - 27 July 2022: Record last updated ### How Precursor Intelligence ranks it CVE-2022-22202 scores **43 out of 100 (Medium)**, with the action "Plan remediation". 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-2022-22202? The published record lists 7 products. Versions are as published: "before 19.1" means every version up to, but not including, 19.1. - [Junos](https://www.precursorintelligence.com/product/juniper/junos) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Operating system): before 19.1, 19.1, 19.1-r1, 19.1-r1-s1, 19.1-r1-s2, 19.1-r1-s3, 19.1-r1-s4, 19.1-r1-s5, 19.1-r1-s6, 19.1-r2, 19.1-r2-s1, 19.1-r2-s2, 19.1-r2-s3, 19.1-r3, 19.1-r3-s1, 19.1-r3-s2, 19.1-r3-s3, 19.1-r3-s4, 19.1-r3-s5, 19.1-r3-s6, 19.1-r3-s7, 19.1-r3-s8, 19.2, 19.2-r1, 19.2-r1-s1, 19.2-r1-s2, 19.2-r1-s3, 19.2-r1-s4, 19.2-r1-s5, 19.2-r1-s6, 19.2-r1-s7, 19.2-r1-s8, 19.2-r1-s9, 19.2-r2, 19.2-r2-s1, 19.2-r3, 19.2-r3-s1, 19.2-r3-s2, 19.2-r3-s3, 19.2-r3-s4 and 110 more - [Ptx1000](https://www.precursorintelligence.com/product/juniper/ptx1000) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Ptx10002-60c](https://www.precursorintelligence.com/product/juniper/ptx10002-60c) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Ptx10008](https://www.precursorintelligence.com/product/juniper/ptx10008) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Ptx10016](https://www.precursorintelligence.com/product/juniper/ptx10016) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Ptx3000](https://www.precursorintelligence.com/product/juniper/ptx3000) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified - [Ptx5000](https://www.precursorintelligence.com/product/juniper/ptx5000) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Hardware): version not specified ## How do I fix CVE-2022-22202? 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/JSA69706) (Exploit, Mitigation, Vendor advisory) ## Questions ### What is CVE-2022-22202? CVE-2022-22202 is a medium-severity flaw in Junos from Juniper, published on 20 July 2022. An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can take it offline. ### How serious is CVE-2022-22202? It scores 6.5 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2022-22202 is 43 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2022-22202 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.5%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2022-22202 affect? For Junos from Juniper: before 19.1, 19.1, 19.1-r1, 19.1-r1-s1, 19.1-r1-s2, 19.1-r1-s3 and 144 more. The record lists 7 products in all, each with its versions, under "Who is affected" on this page. ### How do I fix CVE-2022-22202? 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-2022-22202 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