# CVE-2017-1000357: Denial of service in n/a

> Attackers can cause a denial of service in OpenDaylight by triggering packet rejection from the controller.

- **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-47cr-xw67-rm48

## What is CVE-2017-1000357?

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

### Official description

Denial of Service attack when the switch rejects to receive packets from the controller. Component: This vulnerability affects OpenDaylight odl-l2switch-switch, which is the feature responsible for the OpenFlow communication. Version: OpenDaylight versions 3.3 (Lithium-SR3), 3.4 (Lithium-SR4), 4.0 (Beryllium), 4.1 (Beryllium-SR1), 4.2 (Beryllium-SR2), and 4.4 (Beryllium-SR4) are affected by this flaw. Java version is openjdk version 1.8.0_91.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Opendaylight Opendaylight.

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

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

## Is CVE-2017-1000357 being exploited?

There is no known exploitation of CVE-2017-1000357 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-1778](https://insights.sbomify.com/CVE-2015-1778/): Opendaylight will authenticate any username and password combination (critical 9.8)
- [CVE-2017-1000411](https://insights.sbomify.com/CVE-2017-1000411/): Denial of service in n/a (high 7.5)
- [CVE-2017-1000361](https://insights.sbomify.com/CVE-2017-1000361/): OpenDaylight Controller DoS (high 7.5)
- [CVE-2014-5035](https://insights.sbomify.com/CVE-2014-5035/): XML external entity in n/a (medium 6.8)
- [CVE-2017-1000358](https://insights.sbomify.com/CVE-2017-1000358/): Null dereference in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000357 and fix it if it is affected.

What it is: CVE-2017-1000357 is a high-severity denial of service vulnerability in n/a, 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-1000357 in the wild and no public exploit code.

Affected product: n/a. 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-1000357/ (Markdown: https://insights.sbomify.com/CVE-2017-1000357/index.md)
```

## Sources

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

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