# CVE-2024-21590: Junos OS Evolved: Packets which are not destined to the device can reach the RE

> An unauthenticated attacker within the MPLS domain can cause a Denial of Service on the Routing Engine by sending crafted transit MPLS IPv4 packets.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-53r8-h9fr-mwc7

## What is CVE-2024-21590?

CVE-2024-21590 is a high-severity denial of service vulnerability in Juniper Junos Os Evolved, published on 12 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Improper Input Validation vulnerability in Juniper Tunnel Driver (jtd) and ICMP module of Juniper Networks Junos OS Evolved allows an unauthenticated attacker within the MPLS administrative domain to send specifically crafted packets to the Routing Engine (RE) to cause a Denial of Service (DoS). 

When specifically crafted transit MPLS IPv4 packets are received by the Packet Forwarding Engine (PFE), these packets are internally forwarded to the RE. Continued receipt of these packets may create a sustained Denial of Service (DoS) condition.

This issue affects Juniper Networks Junos OS:

  *  All versions before 21.2R3-S8-EVO;
  *  from 21.4-EVO before 21.4R3-S6-EVO;
  *  from 22.2-EVO before 22.2R3-S4-EVO;
  *  from 22.3-EVO before 22.3R3-S3-EVO;
  *  from 22.4-EVO before 22.4R3-EVO;
  *  from 23.2-EVO before 23.2R2-EVO.
  *  from 23.4-EVO before 23.4R1-S1-EVO.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Juniper Junos Os Evolved.

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

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

## Is CVE-2024-21590 being exploited?

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

## Other vulnerabilities in Juniper Junos Os Evolved

- [CVE-2026-21902](https://insights.sbomify.com/CVE-2026-21902/): Junos OS Evolved: PTX Series: A vulnerability allows a unauthenticated, network-based attacker to execute code as root (critical 9.3)
- [CVE-2023-28983](https://insights.sbomify.com/CVE-2023-28983/): Junos OS Evolved: Shell Injection vulnerability in the gNOI server (high 8.8)
- [CVE-2025-21599](https://insights.sbomify.com/CVE-2025-21599/): Denial of service in Junos OS Evolved (high 8.7)
- [CVE-2024-47502](https://insights.sbomify.com/CVE-2024-47502/): Junos OS Evolved: TCP session state is not always cleared on the Routing Engine leading to DoS (high 8.7)
- [CVE-2024-39531](https://insights.sbomify.com/CVE-2024-39531/): Junos OS Evolved: ACX 7000 Series: Protocol specific DDoS configuration affects other protocols (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-21590 is a high-severity denial of service vulnerability in Juniper Junos Os Evolved, published on 12 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-21590 in the wild and no public exploit code.

Affected product: Juniper Junos Os Evolved. 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-21590/ (Markdown: https://insights.sbomify.com/CVE-2024-21590/index.md)
```

## Sources

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

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