# CVE-2024-47490: Junos OS Evolved: ACX 7000 Series: Receipt of specific transit MPLS packets causes resources to be exhausted

> An unauthenticated attacker can cause a denial of service on Juniper ACX 7000 routers by sending specific transit MPLS packets that exhaust system resources.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2024
- **Updated:** 11 Oct 2024
- **Also known as:** GHSA-r892-94gp-v735

## What is CVE-2024-47490?

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

### Official description

An Improper Restriction of Communication Channel to Intended Endpoints vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS Evolved on ACX 7000 Series allows an unauthenticated, network based attacker to cause increased consumption of resources, ultimately resulting in a Denial of Service (DoS).

When specific transit MPLS packets are received by the PFE, these packets are internally forwarded to the Routing Engine (RE), rather than being handled appropriately. Continuous receipt of these MPLS packets causes resources to be exhausted. MPLS config is not required to be affected by this issue. 

This issue affects Junos OS Evolved ACX 7000 Series: 

  *  All versions before 21.4R3-S9-EVO,
  *  22.2-EVO before 22.2R3-S4-EVO, 
  *  22.3-EVO before 22.3R3-S3-EVO, 
  *  22.4-EVO before 22.4R3-S2-EVO, 
  *  23.2-EVO before 23.2R2-EVO, 
  *  23.4-EVO before 23.4R1-S1-EVO, 23.4R2-EVO.

Weakness: CWE-923 (Improper Restriction of Communication Channel to Intended Endpoints)

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

It affects 1 product.


Products: Juniper Junos Os Evolved.

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

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

## Is CVE-2024-47490 being exploited?

There is no known exploitation of CVE-2024-47490 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-47490 and fix it if it is affected.

What it is: CVE-2024-47490 is a high-severity denial of service vulnerability in Juniper Junos Os Evolved, published on 11 Oct 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-47490 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-47490/ (Markdown: https://insights.sbomify.com/CVE-2024-47490/index.md)
```

## Sources

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

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