# CVE-2017-2315: Denial of service in Junos OS on EX series Ethernet Switches with IPv6 enabled

> A remote attacker can cause a denial of service on Juniper EX switches via crafted IPv6 Neighbor Discovery packets, leading to memory exhaustion.

- **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:** 24 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xrr6-r4jq-rrhc

## What is CVE-2017-2315?

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

### Official description

On Juniper Networks EX Series Ethernet Switches running affected Junos OS versions, a vulnerability in IPv6 processing has been discovered that may allow a specially crafted IPv6 Neighbor Discovery (ND) packet destined to an EX Series Ethernet Switch to cause a slow memory leak. A malicious network-based packet flood of these crafted IPv6 NDP packets may eventually lead to resource exhaustion and a denial of service. The affected Junos OS versions are: 12.3 prior to 12.3R12-S4, 12.3R13; 13.3 prior to 13.3R10; 14.1 prior to 14.1R8-S3, 14.1R9; 14.1X53 prior ro 14.1X53-D12, 14.1X53-D40; 14.1X55 prior to 14.1X55-D35; 14.2 prior to 14.2R6-S4, 14.2R7-S6, 14.2R8; 15.1 prior to 15.1R5; 16.1 before 16.1R3; 16.2 before 16.2R1-S3, 16.2R2. 17.1R1 and all subsequent releases have a resolution for this vulnerability.

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime)

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2017-2315 being exploited?

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

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

## Sources

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

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