# CVE-2014-0617: Denial of service in n/a

> Remote attackers can crash the flowd process on Juniper SRX gateways by sending a crafted IP packet, causing a denial of service.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qg26-3hrv-wfpg

## What is CVE-2014-0617?

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

### Official description

Juniper Junos 10.4S before 10.4S15, 10.4R before 10.4R16, 11.4 before 11.4R9, and 12.1R before 12.1R7 on SRX Series service gateways allows remote attackers to cause a denial of service (flowd crash) via a crafted IP packet.

## Which versions are affected by CVE-2014-0617?

It affects 13 products.


Products: Juniper Junos, Juniper Srx100, Juniper Srx110, Juniper Srx1400, Juniper Srx210, Juniper Srx220, Juniper Srx240, Juniper Srx3400, Juniper Srx3600, Juniper Srx550, Juniper Srx5600, Juniper Srx5800, Juniper Srx650.

## How do I fix CVE-2014-0617?

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

## Is CVE-2014-0617 being exploited?

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

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

## Sources

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

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