# CVE-2019-10931: Denial of service in All other SIPROTEC 5 device types with CPU variants CP300 and CP100 and the respective Ethernet communication modules

> Attackers can cause a denial of service on Siemens SIPROTEC 5 devices by sending specially crafted packets to port 443.

- **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:** 11 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jm37-cfmc-68fh

## What is CVE-2019-10931?

CVE-2019-10931 is a high-severity denial of service vulnerability in Siemens AG All other SIPROTEC 5 device types with CPU variants CP300 and CP100 and the respective Ethernet communication modules, published on 11 Jul 2019. 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 All other SIPROTEC 5 device types with CPU variants CP300 and CP100 and the respective Ethernet communication modules (All versions ), DIGSI 5 engineering software (All versions < V7.90), SIPROTEC 5 device types 6MD85, 6MD86, 6MD89, 7UM85, 7SA87, 7SD87, 7SL87, 7VK87, 7SA82, 7SA86, 7SD82, 7SD86, 7SL82, 7SL86, 7SJ86, 7SK82, 7SK85, 7SJ82, 7SJ85, 7UT82, 7UT85, 7UT86, 7UT87 and 7VE85 with CPU variants CP300 and CP100 and the respective Ethernet communication modules (All versions < V7.90), SIPROTEC 5 device types 7SS85 and 7KE85 (All versions < V8.01), SIPROTEC 5 device types with CPU variants CP200 and the respective Ethernet communication modules (All versions < V7.59), SIPROTEC 5 relays with CPU variants CP200 and the respective Ethernet communication modules (All versions < V7.59). Specially crafted packets sent to port 443/TCP could cause a Denial of Service condition.

Weakness: CWE-248 (Uncaught Exception)

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

It affects 2 products.


Products: Siemens Digsi 5 Engineering Software, Siemens Siprotec 5 Digsi Device Driver.

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

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

## Is CVE-2019-10931 being exploited?

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

## Other vulnerabilities in Siemens AG All other SIPROTEC 5 device types with CPU variants CP300 and CP100 and the respective Ethernet communication modules

- [CVE-2019-10930](https://insights.sbomify.com/CVE-2019-10930/): File upload in All other SIPROTEC 5 device types with CPU variants CP300 and CP100 and the respective Ethernet communication modules (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10931 is a high-severity denial of service vulnerability in Siemens AG All other SIPROTEC 5 device types with CPU variants CP300 and CP100 and the respective Ethernet communication modules, published on 11 Jul 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-10931 in the wild and no public exploit code.

Affected product: Siemens AG All other SIPROTEC 5 device types with CPU variants CP300 and CP100 and the respective Ethernet communication modules. 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-10931/ (Markdown: https://insights.sbomify.com/CVE-2019-10931/index.md)
```

## Sources

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

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