# What is CVE-2020-1627?

> CVE-2020-1627 is a high-severity flaw (CVSS 7.5) in Junos from Juniper, published on 8 April 2020. 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 1.3%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2020-1627

## 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:** 46 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes.
- **Severity:** High (CVSS 7.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:** 1.3% (latest exploit-likelihood forecast)
- **Published:** 8 April 2020
- **Record last updated:** 21 July 2021
- **Main product:** Junos from Juniper
- **Affected products:** 3

## What is CVE-2020-1627? 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

A vulnerability in Juniper Networks Junos OS on vMX and MX150 devices may allow an attacker to cause a Denial of Service (DoS) by sending specific packets requiring special processing in microcode that the flow cache can't handle, causing the riot forwarding daemon to crash. By continuously sending the same specific packets, an attacker can repeatedly crash the riot process causing a sustained Denial of Service. Flow cache is specific to vMX based products and the MX150, and is enabled by default in performance mode. This issue can only be triggered by traffic destined to the device. Transit traffic will not cause the riot daemon to crash. When the issue occurs, a core dump and riot log file entry are generated. For example: /var/crash/core.J-UKERN.mpc0.1557255993.3864.gz /home/pfe/RIOT logs: fpc0 riot[1888]: PANIC in lu_reorder_send_packet_postproc(): fpc0 riot[6655]: PANIC in lu_reorder_send_packet_postproc(): This issue affects Juniper Networks Junos OS: 18.1 versions prior to 18.1R3 on vMX and MX150; 18.2 versions prior to 18.2R3 on vMX and MX150; 18.2X75 versions prior to 18.2X75-D60 on vMX and MX150; 18.3 versions prior to 18.3R3 on vMX and MX150; 18.4 versions prior to 18.4R2 on vMX and MX150; 19.1 versions prior to 19.1R2 on vMX and MX150. This issue does not affect Junos OS versions prior to 18.1R1.

### 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: 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:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`

## Is CVE-2020-1627 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 1.3%. That can change at any time, which is why we keep watching.

Exploit likelihood over the last 7 days: 1.3%, 1.3%, 1.3%, 1.3%, 1.3%, 1.3%, 1.3%.

### Timeline

- 8 April 2020: Published
- 21 July 2021: Record last updated

### How Precursor Intelligence ranks it

CVE-2020-1627 scores **46 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-2020-1627?

The published record lists 3 products.

- [Junos](https://www.precursorintelligence.com/product/juniper/junos) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Operating system): 18.1, 18.1-r2, 18.1-r2-s1, 18.1-r2-s2, 18.1-r2-s4, 18.2, 18.2-r1, 18.2-r1-s3, 18.2-r1-s5, 18.2-r2-s1, 18.2-r2-s2, 18.2-r2-s3, 18.2-r2-s4, 18.2-r2-s5, 18.2-r2-s6, 18.2x75, 18.2x75-d20, 18.2x75-d30, 18.2x75-d40, 18.3, 18.3-r1, 18.3-r1-s1, 18.3-r1-s2, 18.3-r1-s3, 18.3-r1-s5, 18.3-r2, 18.3-r2-s1, 18.3-r2-s2, 18.4, 18.4-r1, 18.4-r1-s1, 18.4-r1-s2, 18.4-r1-s5, 19.1, 19.1-r1, 19.1-r1-s1, 19.1-r1-s2, 19.1-r1-s3
- [Mx150](https://www.precursorintelligence.com/product/juniper/mx150) 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) (Application): version not specified

## How do I fix CVE-2020-1627?

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/JSA11006) (Vendor advisory)

## Questions

### What is CVE-2020-1627?

CVE-2020-1627 is a high-severity flaw in Junos from Juniper, published on 8 April 2020. 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-2020-1627?

It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2020-1627 is 46 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-2020-1627 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 1.3%. That can change at any time, which is why we keep watching.

### Which versions does CVE-2020-1627 affect?

For Junos from Juniper: 18.1, 18.1-r2, 18.1-r2-s1, 18.1-r2-s2, 18.1-r2-s4, 18.2 and 32 more. The record lists 3 products in all, each with its versions, under "Who is affected" on this page.

### How do I fix CVE-2020-1627?

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-2020-1627 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