# CVE-2024-21612: Junos OS Evolved: Specific TCP traffic causes OFP core and restart of RE

> Unauthenticated attackers can cause a denial of service by sending specific TCP packets to the OFP service, crashing the Routing Engine.

- **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:** 12 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-rj85-c5h6-pfrr

## What is CVE-2024-21612?

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

### Official description

An Improper Handling of Syntactically Invalid Structure vulnerability in Object Flooding Protocol (OFP) service of Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS).

On all Junos OS Evolved platforms, when specific TCP packets are received on an open OFP port, the OFP crashes leading to a restart of Routine Engine (RE). Continuous receipt of these specific TCP packets will lead to a sustained Denial of Service (DoS) condition.

This issue affects:

Juniper Networks Junos OS Evolved

  *  All versions earlier than 21.2R3-S7-EVO;
  *  21.3 versions earlier than 21.3R3-S5-EVO ;
  *  21.4 versions earlier than 21.4R3-S5-EVO;
  *  22.1 versions earlier than 22.1R3-S4-EVO;
  *  22.2 versions earlier than 22.2R3-S3-EVO ;
  *  22.3 versions earlier than 22.3R3-EVO;
  *  22.4 versions earlier than 22.4R2-EVO, 22.4R3-EVO.

Weakness: CWE-228 (Improper Handling of Syntactically Invalid Structure)

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

It affects 1 product.


Products: Juniper Junos Os Evolved.

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

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

## Is CVE-2024-21612 being exploited?

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

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

## Sources

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

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