# CVE-2024-39552: Junos OS and Junos OS Evolved: Malformed BGP UPDATE causes RPD crash

> A remote attacker can crash the routing daemon by sending malformed BGP UPDATE packets, causing a denial of service on Juniper network 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/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 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-3fgw-53wh-c98c

## What is CVE-2024-39552?

CVE-2024-39552 is a high-severity denial of service vulnerability in Juniper Junos, published on 11 Jul 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 cause the RPD process to crash leading to a Denial of Service (DoS).

When a malformed BGP UPDATE packet is received over an established BGP session, RPD crashes and restarts.

Continuous receipt of the malformed BGP UPDATE messages will create a sustained Denial of Service (DoS) condition for impacted devices.

This issue affects eBGP and iBGP, in both IPv4 and IPv6 implementations.  This issue requires a remote attacker to have at least one established BGP session.

This issue affects:
 
Juniper Networks Junos OS:
  *  All versions earlier than 20.4R3-S9;
  *  21.2 versions earlier than 21.2R3-S7;
  *  21.3 versions earlier than 21.3R3-S5;
  *  21.4 versions earlier than 21.4R3-S6;
  *  22.1 versions earlier than 22.1R3-S4;
  *  22.2 versions earlier than 22.2R3-S3;
  *  22.3 versions earlier than 22.3R3-S2;
  *  22.4 versions earlier than 22.4R3;
  *  23.2 versions earlier than 23.2R2.

Juniper Networks Junos OS Evolved:
  *  All versions earlier than 21.2R3-S7;
  *  21.3-EVO versions earlier than 21.3R3-S5;
  *  21.4-EVO versions earlier than 21.4R3-S8;
  *  22.1-EVO versions earlier than 22.1R3-S4;
  *  22.2-EVO versions earlier than 22.2R3-S3;
  *  22.3-EVO versions earlier than 22.3R3-S2;
  *  22.4-EVO versions earlier than 22.4R3;
  *  23.2-EVO versions earlier than 23.2R2.

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

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

It affects 2 products.


Products: Juniper Junos, Juniper Junos Os Evolved.

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

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

## Is CVE-2024-39552 being exploited?

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

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

## Sources

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

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