# CVE-2019-19281: Denial of service in SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants)

> Unauthenticated attackers can cause denial of service on Siemens SIMATIC controllers by sending specially 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4cqc-hc5r-xhj6

## What is CVE-2019-19281?

CVE-2019-19281 is a high-severity denial of service vulnerability in Siemens AG SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants), published on 10 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been identified in SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants) (All versions >= V2.5 and < V20.8), SIMATIC S7-1500 CPU family (incl. related ET200 CPUs and SIPLUS variants) (All versions >= V2.5 and < V2.8), SIMATIC S7-1500 Software Controller (All versions >= V2.5 and < V20.8). Affected devices contain a vulnerability that allows an unauthenticated attacker to trigger a Denial-of-Service condition. The vulnerability can be triggered if specially crafted UDP packets are sent to the device. The security vulnerability could be exploited by an attacker with network access to the affected systems. Successful exploitation requires no system privileges and no user interaction. An attacker could use the vulnerability to compromise the device availability.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 14 products.


Products: Siemens Simatic Et 200sp Open Controller Cpu 1515sp Pc2 Firmware, Siemens Simatic S7-1500 Cpu 1507s F Firmware, Siemens Simatic S7-1500 Cpu 1507s Firmware, Siemens Simatic S7-1500 Cpu 1508s F Firmware, Siemens Simatic S7-1500 Cpu 1508s Firmware, Siemens Simatic S7-1500 Cpu 1511-1 Pn Firmware, Siemens Simatic S7-1500 Cpu 1513-1 Pn Firmware, Siemens Simatic S7-1500 Cpu 1515-2 Pn Firmware, Siemens Simatic S7-1500 Cpu 1516-3 Dp Firmware, Siemens Simatic S7-1500 Cpu 1516-3 Pn Firmware, Siemens Simatic S7-1500 Cpu 1517-3 Dp Firmware, Siemens Simatic S7-1500 Cpu 1517-3 Pn Firmware, Siemens Simatic S7-1500 Cpu 1518-4 Dp Firmware, Siemens Simatic S7-1500 Cpu 1518-4 Pn Firmware.

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

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

## Is CVE-2019-19281 being exploited?

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

## Other vulnerabilities in Siemens AG SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants)

- [CVE-2019-10943](https://insights.sbomify.com/CVE-2019-10943/): A vulnerability has been identified in SIMATIC Drive Controller family (All versions), SIMATIC ET 200SP Open Controller CPU 1515SP PC (incl. (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19281 and fix it if it is affected.

What it is: CVE-2019-19281 is a high-severity denial of service vulnerability in Siemens AG SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants), published on 10 Mar 2020. 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-19281 in the wild and no public exploit code.

Affected product: Siemens AG SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants). 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-19281/ (Markdown: https://insights.sbomify.com/CVE-2019-19281/index.md)
```

## Sources

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

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