# CVE-2024-21586: Junos OS: SRX Series and NFX Series: Specific valid traffic leads to a PFE crash

> An unauthenticated attacker can cause a Packet Forwarding Engine crash and restart by sending specific valid traffic, resulting in a sustained Denial-of-Service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-w2xf-42w4-qqrc

## What is CVE-2024-21586?

CVE-2024-21586 is a high-severity denial of service vulnerability in Juniper Junos, published on 1 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Improper Check for Unusual or Exceptional Conditions vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on SRX Series and NFX Series allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS).

If an affected device receives specific valid traffic destined to the device, it will cause the PFE to crash and restart.  Continued receipt and processing of this traffic will create a sustained DoS condition.

This issue affects Junos OS on SRX Series:

  *  21.4 versions before 21.4R3-S7.9,
  *  22.1 versions before 22.1R3-S5.3,
  *  22.2 versions before 22.2R3-S4.11,
  *  22.3 versions before 22.3R3,
  *  22.4 versions before 22.4R3.

This issue affects Junos OS on NFX Series:

  *  21.4 versions before 21.4R3-S8,
  *  22.1 versions after 22.1R1,
  *  22.2 versions before 22.2R3-S5,
  *  22.3 versions before 22.3R3,
  *  22.4 versions before 22.4R3.

Junos OS versions prior to 21.4R1 are not affected by this issue.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

## Which versions are affected by CVE-2024-21586?

It affects 1 product.


Products: Juniper Junos.

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

No fix has been published for CVE-2024-21586 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-21586 being exploited?

There is no known exploitation of CVE-2024-21586 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-21586 and fix it if it is affected.

What it is: CVE-2024-21586 is a high-severity denial of service vulnerability in Juniper Junos, published on 1 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-21586 in the wild and no public exploit code.

Affected product: Juniper Junos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-21586/ (Markdown: https://insights.sbomify.com/CVE-2024-21586/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-21586
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-21586
- OSV: https://osv.dev/vulnerability/CVE-2024-21586

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-21586/
Summaries are generated and may contain mistakes; the official description above is the record.