# CVE-2017-2301: Denial of service in Junos OS with DHCPv6 enabled

> A crafted DHCPv6 packet causes the jdhcpd daemon to crash, leading to a denial of service for IPv6 subscribers on Juniper devices.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 30 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-49g9-wfgx-238p

## What is CVE-2017-2301?

CVE-2017-2301 is a high-severity denial of service vulnerability in Juniper Junos, published on 30 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On Juniper Networks products or platforms running Junos OS 11.4 prior to 11.4R13-S3, 12.1X46 prior to 12.1X46-D60, 12.3 prior to 12.3R12-S2 or 12.3R13, 12.3X48 prior to 12.3X48-D40, 13.2X51 prior to 13.2X51-D40, 13.3 prior to 13.3R10, 14.1 prior to 14.1R8, 14.1X53 prior to 14.1X53-D12 or 14.1X53-D35, 14.1X55 prior to 14.1X55-D35, 14.2 prior to 14.2R7, 15.1 prior to 15.1F6 or 15.1R3, 15.1X49 prior to 15.1X49-D60, 15.1X53 prior to 15.1X53-D30 and DHCPv6 enabled, when a crafted DHCPv6 packet is received from a subscriber, jdhcpd daemon crashes and restarts. Repeated crashes of the jdhcpd process may constitute an extended denial of service condition for subscribers attempting to obtain IPv6 addresses.

## Which versions are affected by CVE-2017-2301?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2017-2301?

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

## Is CVE-2017-2301 being exploited?

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

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

## Sources

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

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