# CVE-2024-30382: Junos OS and Junos OS Evolved: RPD crash when CoS-based forwarding (CBF) policy is configured

> Unauthenticated attackers can cause a denial of service via memory corruption in the routing daemon when CoS-based forwarding is configured.

- **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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-83pq-frch-8xf2

## What is CVE-2024-30382?

CVE-2024-30382 is a high-severity memory corruption vulnerability in Juniper Junos, published on 12 Apr 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 routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based, unauthenticated attacker to send a specific routing update, causing an rpd core due to memory corruption, leading to a Denial of Service (DoS).

This issue can only be triggered when the system is configured for CoS-based forwarding (CBF) with a policy map containing a cos-next-hop-map action (see below).
This issue affects:
Junos OS: 

  *  all versions before 20.4R3-S10, 
  *  from 21.2 before 21.2R3-S8,
  *  from 21.3 before 21.3R3, 
  *  from 21.4 before 21.4R3, 
  *  from 22.1 before 22.1R2;

Junos OS Evolved: 

  *  all versions before 21.2R3-S8-EVO,
  *  from 21.3 before 21.3R3-EVO, 
  *  from 21.4 before 21.4R3-EVO, 
  *  from 22.1 before 22.1R2-EVO.

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

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

It affects 2 products.


Products: Juniper Junos, Juniper Junos Os Evolved.

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

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

## Is CVE-2024-30382 being exploited?

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

What it is: CVE-2024-30382 is a high-severity memory corruption vulnerability in Juniper Junos, published on 12 Apr 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-30382 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-30382/ (Markdown: https://insights.sbomify.com/CVE-2024-30382/index.md)
```

## Sources

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

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