# CVE-2017-10619: Junos: SRX cluster denial of service vulnerability in flowd due to multicast packets

> Attackers can cause a denial of service on Juniper SRX firewalls by sending multicast packets when Express Path is enabled.

- **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:** 13 Oct 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7x82-gf29-pfxv

## What is CVE-2017-10619?

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

### Official description

When Express Path (formerly known as service offloading) is configured on Juniper Networks SRX1400, SRX3400, SRX3600, SRX5400, SRX5600, SRX5800 in high availability cluster configuration mode, certain multicast packets might cause the flowd process to crash, halting or interrupting traffic from flowing through the device and triggering RG1+ (data-plane) fail-over to the secondary node. Repeated crashes of the flowd process may constitute an extended denial of service condition. This service is not enabled by default and is only supported in high-end SRX platforms. Affected releases are Juniper Networks Junos OS 12.3X48 prior to 12.3X48-D45, 15.1X49 prior to 15.1X49-D80 on SRX1400, SRX3400, SRX3600, SRX5400, SRX5600, SRX5800.

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2017-10619 being exploited?

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

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

## Sources

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

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