# CVE-2017-10613: Junos OS: A kernel hang may occur due to a specific loopback filter action command

> An attacker with CLI access can hang the kernel by issuing a specific loopback filter command, causing a denial of service on Juniper devices.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-f8w4-v283-r8w8

## What is CVE-2017-10613?

CVE-2017-10613 is a medium-severity denial of service vulnerability in Juniper Junos, published on 13 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in a specific loopback filter action command, processed in a specific logical order of operation, in a running configuration of Juniper Networks Junos OS, allows an attacker with CLI access and the ability to initiate remote sessions to the loopback interface with the defined action, to hang the kernel. Affected releases are Juniper Networks Junos OS 12.1X46 prior to 12.1X46-D55; 12.3X48 prior to 12.3X48-D35; 14.1 prior to 14.1R8-S4, 14.1R9; 14.1X53 prior to 14.1X53-D40; 14.2 prior to 14.2R4-S9, 14.2R7-S8, 14.2R8; 15.1 prior to 15.1F5-S3, 15.1F6, 15.1R4; 15.1X49 prior to 15.1X49-D60; 15.1X53 prior to 15.1X53-D47; 16.1 prior to 16.1R2. No other Juniper Networks products or platforms are affected by this issue.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2017-10613 being exploited?

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

What it is: CVE-2017-10613 is a medium-severity denial of service vulnerability in Juniper Junos, published on 13 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10613 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-10613/ (Markdown: https://insights.sbomify.com/CVE-2017-10613/index.md)
```

## Sources

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

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