dbcve.org
Pcs 7Application · Siemens

CVE-2017-6865

MEDIUM · 6.5 CVSS v3.0 Published 2017-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Specially crafted PROFINET DCP broadcast packets sent on a local Ethernet segment (Layer 2) can cause a denial-of-service condition in affected Siemens SIMATIC products. The vulnerability affects multiple products including PST, SIMATIC Automation Tool, SIMATIC NET PC-Software, SIMATIC PCS 7, STEP 7 (TIA Portal and V5.X), WinAC, WinCC, and related tools. Services require manual restart to recover.

MitigationApply vendor-supplied patches to all affected products (version thresholds vary by product: e.g., PST to V4.2 HF1, SIMATIC Automation Tool to V3.0, STEP 7 V5.X to V5.6). Implement network segmentation to restrict Layer 2 access to trusted devices only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pcs 7Application
Affected:all versions
Primary Setup ToolApplication
Affected:all versions
Security Configuration ToolApplication
Affected:all versions
Simatic Automation ToolApplication
Affected:all versions
Simatic Net Pc SoftwareApplication
Affected:all versions
Simatic Step 7 \(tia Portal\)Application
Affected:= 5.0= 13.0= 14.0
Simatic Step 7 Micro\/win SmartApplication
Affected:all versions
Simatic Winac Rtx 2010Application
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Siemens SIMATIC products
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -match 'SIMATIC|STEP 7|PCS 7|WinCC|WinAC|Primary Setup Tool|Security Configuration|Automation Tool|NET PC'}, or check C:\Program Files\Siemens for installed software folders
    Affected if Any of the following products are present: PCS 7, Primary Setup Tool, Security Configuration Tool, SIMATIC Automation Tool, SIMATIC NET PC Software, STEP 7 (TIA Portal or V5.X), STEP 7 Micro/Win Smart, or WinAC RTX 2010
  2. Verify product version against affected ranges
    For each installed product, note the exact version from Programs and Features or the product's About/Help menu. Compare to: STEP 7 TIA Portal versions 5.0, 13.0, or 14.0 are affected; all other listed products are affected in ALL versions
    Affected if Installed version matches 5.0, 13.0, or 14.0 for TIA Portal, or any version for PCS 7, PST, Security Configuration Tool, Automation Tool, NET PC Software, Micro/Win Smart, or WinAC RTX 2010
  3. Determine PROFINET network exposure
    Check if the system network adapter is configured for or connected to a PROFINET network. Run 'ipconfig /all' to identify network adapters. Check Windows Services for PROFINET-related services (look for 'PROFINET' in service names). Inspect network switches for PROFINET VLAN configuration or DCP multicast traffic (monitor for packets with Ethernet type 0x8892 or destination MAC 01-0e-cf-00-00-00)
    Affected if The system is on a Layer 2 network segment where PROFINET DCP broadcast packets can be received, or PROFINET services are running
  4. Check for manual service restart capability
    Open Windows Services (services.msc) and locate SIMATIC-related services. Document which services exist and their current status to establish baseline for potential manual restart requirement described in the CVE
    Affected if SIMATIC-related services are present and can be impacted, requiring manual restart per the CVE description

A user is affected if they have any of the listed Siemens products installed on a system connected to a network segment where PROFINET DCP broadcast packets can be received, since all listed product versions are vulnerable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches to all affected products (version thresholds vary by product: e.g., PST to V4.2 HF1, SIMATIC Automation Tool to V3.0, STEP 7 V5.X to V5.6). Implement network segmentation to restrict Layer 2 access to trusted devices only.

Fix this in Pcs 7 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6865 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-6865 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data