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

> Unauthenticated remote attackers can cause denial of service on Siemens PROFINET IO devices by sending crafted UDP packets.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vr9v-38cg-fjfp

## What is CVE-2019-10936?

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

### Official description

Affected devices improperly handle large amounts of specially crafted UDP packets.

This could allow an unauthenticated remote attacker to trigger a denial of service condition.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2019-10936?

It affects 66 products.


Products: Siemens Dk Standard Ethernet Controller Firmware, Siemens Ek-Ertec 200 Firmware, Siemens Ek-Ertec 200p Firmware, Siemens Simatic Cfu Pa Firmware, Siemens Simatic Et 200al Firmware, Siemens Simatic Et 200ecopn Firmware, Siemens Simatic Et 200m Firmware, Siemens Simatic Et 200mp Im 155-5 Pn Ba Firmware, Siemens Simatic Et 200mp Im 155-5 Pn Hf Firmware, Siemens Simatic Et 200mp Im 155-5 Pn St Firmware, Siemens Simatic Et 200pro Firmware, Siemens Simatic Et 200s Firmware, Siemens Simatic Et 200sp Im 155-6 Pn\/2 Hf Firmware, Siemens Simatic Et 200sp Im 155-6 Pn\/3 Hf Firmware, Siemens Simatic Et 200sp Im 155-6 Pn Ba Firmware, Siemens Simatic Et 200sp Im 155-6 Pn Ha Firmware, Siemens Simatic Et 200sp Im 155-6 Pn Hf Firmware, Siemens Simatic Et 200sp Im 155-6 Pn Hs Firmware, Siemens Simatic Et 200sp Im 155-6 Pn St Firmware, Siemens Simatic Hmi Comfort Outdoor Panels 15\" Firmware and 46 more.

## How do I fix CVE-2019-10936?

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

## Is CVE-2019-10936 being exploited?

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

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

## Sources

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

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