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

> Attackers can cause denial of service on Siemens PROFINET IO devices by sending crafted UDP packets to port 161, requiring manual restarts.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-89jc-9q2j-97hr

## What is CVE-2017-12741?

CVE-2017-12741 is a high-severity denial of service vulnerability in Siemens Development/Evaluation Kits for PROFINET IO: DK Standard Ethernet Controller, published on 26 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Specially crafted packets sent to port 161/udp could cause a denial of service condition. The affected devices must be restarted manually.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 38 products.


Products: Siemens Dk Standard Ethernet Controller Firmware, Siemens Ek-Ertec 200p Firmware, Siemens Ek-Ertec 200pn Io Firmware, Siemens Simatic Compact Field Unit Firmware, Siemens Simatic Et 200al Firmware, Siemens Simatic Et 200ecopn Firmware, Siemens Simatic Et 200m Firmware, Siemens Simatic Et 200mp Firmware, Siemens Simatic Et 200pro Firmware, Siemens Simatic Et 200s Firmware, Siemens Simatic Et 200sp Firmware, Siemens Simatic Pn\/Pn Coupler Firmware, Siemens Simatic S7-1200 Firmware, Siemens Simatic S7-1500 Controller Firmware, Siemens Simatic S7-1500 Firmware, Siemens Simatic S7-200 Firmware, Siemens Simatic S7-300 Firmware, Siemens Simatic S7-400h V6 Firmware, Siemens Simatic S7-400pn\/Dp V7 Firmware, Siemens Simatic S7-400pn V6 Firmware and 18 more.

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

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

## Is CVE-2017-12741 being exploited?

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

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

- [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-2680](https://insights.sbomify.com/CVE-2017-2680/): Denial of service in Development/Evaluation Kits for PROFINET IO: DK Standard Ethernet Controller (high 7.1)
- [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-12741 and fix it if it is affected.

What it is: CVE-2017-12741 is a high-severity denial of service vulnerability in Siemens Development/Evaluation Kits for PROFINET IO: DK Standard Ethernet Controller, published on 26 Dec 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-12741 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-12741/ (Markdown: https://insights.sbomify.com/CVE-2017-12741/index.md)
```

## Sources

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

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