# CVE-2024-21614: Junos OS and Junos OS Evolved: A specific query via DREND causes rpd crash

> Unauthenticated attackers can crash the routing daemon via specific DREND queries when NETCONF and gRPC are enabled, causing denial of service.

- **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-v9j6-rmvq-8674

## What is CVE-2024-21614?

CVE-2024-21614 is a high-severity denial of service vulnerability in Juniper Junos, 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 Check for Unusual or Exceptional Conditions vulnerability in Routing Protocol Daemon (RPD) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based, unauthenticated attacker to cause rpd to crash, leading to Denial of Service (DoS).

On all Junos OS and Junos OS Evolved platforms, when NETCONF and gRPC are enabled, and a specific query is executed via Dynamic Rendering (DREND), rpd will crash and restart. Continuous execution of this specific query will cause a sustained Denial of Service (DoS) condition.

This issue affects:

Juniper Networks Junos OS

  *  22.2 versions earlier than 22.2R2-S2, 22.2R3;
  *  22.3 versions earlier than 22.3R2, 22.3R3.

Juniper Networks Junos OS Evolved

  *  22.2 versions earlier than 22.2R2-S2-EVO, 22.2R3-EVO;
  *  22.3 versions earlier than 22.3R2-EVO, 22.3R3-EVO.

This issue does not affect Juniper Networks:

Junos OS versions earlier than 22.2R1;

Junos OS Evolved versions earlier than 22.2R1-EVO.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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

It affects 2 products.


Products: Juniper Junos, Juniper Junos Os Evolved.

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

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

## Is CVE-2024-21614 being exploited?

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

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-21614 is a high-severity denial of service vulnerability in Juniper Junos, 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-21614 in the wild and no public exploit code.

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

## Sources

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

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