# CVE-2017-6865: Denial of service in Primary Setup Tool (PST)

> Attackers can cause denial of service in Siemens industrial software by sending crafted PROFINET DCP broadcast packets on the local network.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8jhv-ch7h-fqpj

## What is CVE-2017-6865?

CVE-2017-6865 is a medium-severity denial of service vulnerability in Siemens AG Primary Setup Tool (PST), published on 11 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been identified in Primary Setup Tool (PST) (All versions < V4.2 HF1), SIMATIC Automation Tool (All versions < V3.0), SIMATIC NET PC-Software (All versions < V14 SP1), SIMATIC PCS 7 V8.1 (All versions), SIMATIC PCS 7 V8.2 (All versions < V8.2 SP1), SIMATIC STEP 7 (TIA Portal) V13 (All versions < V13 SP2), SIMATIC STEP 7 (TIA Portal) V14 (All versions < V14 SP1), SIMATIC STEP 7 V5.X (All versions < V5.6), SIMATIC WinAC RTX 2010 SP2 (All versions), SIMATIC WinAC RTX F 2010 SP2 (All versions), SIMATIC WinCC (TIA Portal) V13 (All versions < V13 SP2), SIMATIC WinCC (TIA Portal) V14 (All versions < V14 SP1), SIMATIC WinCC V7.2 and prior (All versions), SIMATIC WinCC V7.3 (All versions < V7.3 Update 15), SIMATIC WinCC V7.4 (All versions < V7.4 SP1 Upd1), SIMATIC WinCC flexible 2008 (All versions < flexible 2008 SP5), SINAUT ST7CC (All versions installed in conjunction with SIMATIC WinCC < V7.3 Update 15), SINEMA Server (All versions < V14), SINUMERIK 808D Programming Tool (All versions < V4.7 SP4 HF2), SMART PC Access (All versions < V2.3), STEP 7 - Micro/WIN SMART (All versions < V2.3), Security Configuration Tool (SCT) (All versions < V5.0). Specially crafted PROFINET DCP broadcast packets sent to the affected products on a local Ethernet segment (Layer 2) could cause a Denial-of-Service condition of some services. The services require manual restart to recover.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 16 products.


Products: Siemens Pcs 7, Siemens Primary Setup Tool, Siemens Security Configuration Tool, Siemens Simatic Automation Tool, Siemens Simatic Net Pc-Software, Siemens Simatic Step 7 \(Tia Portal\), Siemens Simatic Step 7 Micro\/Win Smart, Siemens Simatic Winac Rtx 2010, Siemens Simatic Winac Rtx F 2010, Siemens Simatic Wincc, Siemens Simatic Wincc \(Tia Portal\), Siemens Simatic Wincc Flexible 2008, Siemens Sinaut St7cc, Siemens Sinema Server, Siemens Sinumerik 808d Programming Tool, Siemens Smart Pc Access.

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

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

## Is CVE-2017-6865 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6865 and fix it if it is affected.

What it is: CVE-2017-6865 is a medium-severity denial of service vulnerability in Siemens AG Primary Setup Tool (PST), published on 11 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6865 in the wild and no public exploit code.

Affected product: Siemens AG Primary Setup Tool (PST). 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-6865/ (Markdown: https://insights.sbomify.com/CVE-2017-6865/index.md)
```

## Sources

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

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