# What is CVE-2024-30387?

> CVE-2024-30387 is a high-severity flaw (CVSS 7.1) in Junos from Juniper, published on 12 April 2024. 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.2%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2024-30387

## 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:** High (CVSS 7.1 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.2% (latest exploit-likelihood forecast)
- **Published:** 12 April 2024
- **Record last updated:** 17 June 2026
- **Main product:** Junos from Juniper
- **Affected products:** 1

## What is CVE-2024-30387? In plain terms

An attacker has to be on the same local network without logging in, and nobody has to click anything.

### The official description

A Missing Synchronization vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on ACX5448 and ACX710 allows an unauthenticated, adjacent attacker to cause a Denial-of-Service (DoS).

If an interface flaps while the system gathers statistics on that interface, two processes simultaneously access a shared resource which leads to a PFE crash and restart.

This issue affects Junos OS:

  *  All versions before 20.4R3-S9,
  *  21.2 versions before 21.2R3-S5, 
  *  21.3 versions before 21.3R3-S5, 
  *  21.4 versions before 21.4R3-S4,
  *  22.1 versions before 22.1R3-S2,
  *  22.2 versions before 22.2R3-S2,
  *  22.3 versions before 22.3R2-S2, 22.3R3,
  *  22.4 versions before 22.4R2.

### What kind of flaw is it?

- CWE-662: Improper Synchronization
- CWE-820: Missing Synchronization

### 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

Severity vector: `CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X`

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

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

### Timeline

- 12 April 2024: Published
- 17 June 2026: Record last updated

### How Precursor Intelligence ranks it

CVE-2024-30387 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-2024-30387?

The published record lists 1 product. Versions are as published: "before 20.4" means every version up to, but not including, 20.4.

- [Junos](https://www.precursorintelligence.com/product/juniper/junos) by [Juniper](https://www.precursorintelligence.com/vendors/juniper) (Operating system): before 20.4, 20.4, 20.4-r1, 20.4-r1-s1, 20.4-r2, 20.4-r2-s1, 20.4-r2-s2, 20.4-r3, 20.4-r3-s1, 20.4-r3-s2, 20.4-r3-s3, 20.4-r3-s4, 20.4-r3-s5, 20.4-r3-s6, 20.4-r3-s7, 20.4-r3-s8, 21.2, 21.2-r1, 21.2-r1-s1, 21.2-r1-s2, 21.2-r2, 21.2-r2-s1, 21.2-r2-s2, 21.2-r3, 21.2-r3-s1, 21.2-r3-s2, 21.2-r3-s3, 21.2-r3-s4, 21.3, 21.3-r1, 21.3-r1-s1, 21.3-r1-s2, 21.3-r2, 21.3-r2-s1, 21.3-r2-s2, 21.3-r3, 21.3-r3-s1, 21.3-r3-s2, 21.3-r3-s3, 21.3-r3-s4 and 39 more

## How do I fix CVE-2024-30387?

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

- [supportportal.juniper.net](http://supportportal.juniper.net/JSA79187) (Vendor advisory)
- [first.org](https://www.first.org/cvss/calculator/4.0#CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L) (Issue tracking)

## Questions

### What is CVE-2024-30387?

CVE-2024-30387 is a high-severity flaw in Junos from Juniper, published on 12 April 2024. An attacker has to be on the same local network without logging in, and nobody has to click anything.

### How serious is CVE-2024-30387?

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

### Which versions does CVE-2024-30387 affect?

For Junos from Juniper: before 20.4, 20.4, 20.4-r1, 20.4-r1-s1, 20.4-r2, 20.4-r2-s1 and 73 more.

### How do I fix CVE-2024-30387?

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-2024-30387 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