# CVE-2019-19282: Denial of service in OpenPCS 7 V8.1

> An attacker with network access can cause a Denial-of-Service condition in Siemens SIMATIC systems by sending specially crafted messages when encrypted communication is enabled.

- **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 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2pg9-8888-cqmc

## What is CVE-2019-19282?

CVE-2019-19282 is a high-severity denial of service vulnerability in Siemens OpenPCS 7 V8.1, 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 OpenPCS 7 V8.1 (All versions), OpenPCS 7 V8.2 (All versions), OpenPCS 7 V9.0 (All versions < V9.0 Upd3), SIMATIC BATCH V8.1 (All versions), SIMATIC BATCH V8.2 (All versions < V8.2 Upd12), SIMATIC BATCH V9.0 (All versions < V9.0 SP1 Upd5), SIMATIC NET PC Software V14 (All versions < V14 SP1 Update 14), SIMATIC NET PC Software V15 (All versions), SIMATIC NET PC Software V16 (All versions < V16 Update 1), SIMATIC PCS 7 V8.1 (All versions), SIMATIC PCS 7 V8.2 (All versions), SIMATIC PCS 7 V9.0 (All versions < V9.0 SP3), SIMATIC Route Control V8.1 (All versions), SIMATIC Route Control V8.2 (All versions), SIMATIC Route Control V9.0 (All versions < V9.0 Upd4), SIMATIC WinCC (TIA Portal) V13 (All versions < V13 SP2), SIMATIC WinCC (TIA Portal) V14 (All versions < V14 SP1 Update 10), SIMATIC WinCC (TIA Portal) V15.1 (All versions < V15.1 Update 5), SIMATIC WinCC (TIA Portal) V16 (All versions < V16 Update 1), SIMATIC WinCC V7.3 (All versions), SIMATIC WinCC V7.4 (All versions < V7.4 SP1 Update 14), SIMATIC WinCC V7.5 (All versions < V7.5 SP1 Update 1). Through specially crafted messages, when encrypted communication is enabled, an attacker with network access could use the vulnerability to compromise the availability of the system by causing a Denial-of-Service condition.
Successful exploitation requires no system privileges and no user interaction.

Weakness: CWE-131 (Incorrect Calculation of Buffer Size)

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

It affects 6 products.


Products: Siemens Openpcs 7, Siemens Simatic Batch, Siemens Simatic Net Pc, Siemens Simatic Pcs 7, Siemens Simatic Route Control, Siemens Simatic Wincc.

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

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

## Is CVE-2019-19282 being exploited?

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

## Other vulnerabilities in Siemens OpenPCS 7 V8.1

- [CVE-2018-4832](https://insights.sbomify.com/CVE-2018-4832/): Denial of service in OpenPCS 7 V7.1 and earlier (high 7.5)
- [CVE-2023-48363](https://insights.sbomify.com/CVE-2023-48363/): Null dereference in OpenPCS 7 V9.1 (high 7.1)
- [CVE-2023-48364](https://insights.sbomify.com/CVE-2023-48364/): Null dereference in OpenPCS 7 V9.1 (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19282 is a high-severity denial of service vulnerability in Siemens OpenPCS 7 V8.1, 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-19282 in the wild and no public exploit code.

Affected product: Siemens OpenPCS 7 V8.1. 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-19282/ (Markdown: https://insights.sbomify.com/CVE-2019-19282/index.md)
```

## Sources

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

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