# CVE-2024-47502: Junos OS Evolved: TCP session state is not always cleared on the Routing Engine leading to DoS

> Unauthenticated attackers can exhaust kernel resources via TCP sessions, causing denial of service on Junos OS Evolved devices.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:U/RE:M`)
- **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-8pm6-575p-r3mv

## What is CVE-2024-47502?

CVE-2024-47502 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 Allocation of Resources Without Limits or Throttling vulnerability in the kernel of Juniper Networks Junos OS Evolved allows an unauthenticated, network based attacker to cause a Denial of Service (DoS).

In specific cases the state of TCP sessions that are terminated is not cleared, which over time leads to an exhaustion of resources, preventing new connections to the control plane from being established.

A continuously increasing number of connections shown by:

user@host > show system connections

is indicative of the problem. To recover the respective RE needs to be restarted manually.

This issue only affects IPv4 but does not affect IPv6.
This issue only affects TCP sessions established in-band (over an interface on an FPC) but not out-of-band (over the management ethernet port on the routing-engine).

This issue affects Junos OS Evolved: 

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

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Juniper Junos Os Evolved.

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

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

## Is CVE-2024-47502 being exploited?

There is no known exploitation of CVE-2024-47502 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-39531](https://insights.sbomify.com/CVE-2024-39531/): Junos OS Evolved: ACX 7000 Series: Protocol specific DDoS configuration affects other protocols (high 8.7)
- [CVE-2024-39562](https://insights.sbomify.com/CVE-2024-39562/): Junos OS Evolved: A high rate of SSH connections causes a Denial of Service (high 8.7)

## Fix prompt for AI coding agents

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

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

## Sources

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

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