# CVE-2024-47489: Junos OS Evolved: ACX Series: Receipt of specific transit protocol packets is incorrectly processed by the RE

> An unauthenticated attacker can cause a partial denial of service on Juniper ACX devices by sending specific transit protocol packets that trigger DDoS protection violations.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:L/R:A`)
- **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-3x4w-v43m-f5m7

## What is CVE-2024-47489?

CVE-2024-47489 is a medium-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 Handling of Exceptional Conditions vulnerability in the Packet Forwarding Engine (pfe) of the Juniper Networks Junos OS Evolved on ACX Series devices allows an unauthenticated, network based attacker sending specific transit protocol traffic to cause a partial Denial of Service (DoS) to downstream devices.

Receipt of specific transit protocol packets is incorrectly processed by the Routing Engine (RE), filling up the DDoS protection queue which is shared between routing protocols. This influx of transit protocol packets causes DDoS protection violations, resulting in protocol flaps which can affect connectivity to networking devices.

This issue affects both IPv4 and IPv6. This issue does not require any specific routing protocol to be configured or enabled.

The following commands can be used to monitor the DDoS protection queue:

       labuser@re0> show evo-pfemand host pkt-stats

    labuser@re0> show host-path ddos all-policers

This issue affects Junos OS Evolved: 

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

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

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

It affects 1 product.


Products: Juniper Junos Os Evolved.

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

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

## Is CVE-2024-47489 being exploited?

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

What it is: CVE-2024-47489 is a medium-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-47489 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-47489/ (Markdown: https://insights.sbomify.com/CVE-2024-47489/index.md)
```

## Sources

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

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