# CVE-2017-2680: Denial of service in Development/Evaluation Kits for PROFINET IO: DK Standard Ethernet Controller

> Crafted PROFINET DCP packets cause denial of service on Siemens network devices, requiring manual recovery.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2017
- **Updated:** 10 Sep 2024
- **Also known as:** GHSA-4vvg-656r-c25j

## What is CVE-2017-2680?

CVE-2017-2680 is a high-severity denial of service vulnerability in Siemens Development/Evaluation Kits for PROFINET IO: DK Standard Ethernet Controller, published on 11 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Specially crafted PROFINET DCP broadcast packets could cause a denial of service condition of affected products on a local Ethernet segment (Layer 2). Human interaction is required to recover the systems. PROFIBUS interfaces are not affected.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 93 products.


Products: Siemens Dk Standard Ethernet Controller Firmware, Siemens Ek-Ertec 200 Pn Io Firmware, Siemens Ek-Ertec 200p Pn Io Firmware, Siemens Extension Unit 12 Profinet Firmware, Siemens Extension Unit 15 Profinet Firmware, Siemens Extension Unit 19 Profinet Firmware, Siemens Extension Unit 22 Profinet Firmware, Siemens Ie\/As-I Link Pn Io Firmware, Siemens Ie\/Pb-Link Firmware, Siemens Pn\/Pn Coupler Firmware, Siemens Scalance M-800 Firmware, Siemens Scalance S615 Firmware, Siemens Scalance W700 Firmware, Siemens Scalance X200 Firmware, Siemens Scalance X200 Irt Firmware, Siemens Scalance X300 Firmware, Siemens Scalance X408 Firmware, Siemens Scalance X414 Firmware, Siemens Scalance Xm400 Firmware, Siemens Scalance Xr500 Firmware and 73 more.

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

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

## Is CVE-2017-2680 being exploited?

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

## Other vulnerabilities in Siemens Development/Evaluation Kits for PROFINET IO: DK Standard Ethernet Controller

- [CVE-2017-12741](https://insights.sbomify.com/CVE-2017-12741/): Denial of service in Development/Evaluation Kits for PROFINET IO: DK Standard Ethernet Controller (high 8.7)
- [CVE-2019-10936](https://insights.sbomify.com/CVE-2019-10936/): Denial of service in Development/Evaluation Kits for PROFINET IO: DK Standard Ethernet Controller (high 7.5)
- [CVE-2017-2681](https://insights.sbomify.com/CVE-2017-2681/): Denial of service in Development/Evaluation Kits for PROFINET IO: DK Standard Ethernet Controller (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2680 is a high-severity denial of service vulnerability in Siemens Development/Evaluation Kits for PROFINET IO: DK Standard Ethernet Controller, published on 11 May 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-2680 in the wild and no public exploit code.

Affected product: Siemens Development/Evaluation Kits for PROFINET IO: DK Standard Ethernet Controller. 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-2680/ (Markdown: https://insights.sbomify.com/CVE-2017-2680/index.md)
```

## Sources

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

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