dbcve.org
Openpcs 7Application · Siemens

CVE-2019-19282

HIGH · 7.5 CVSS v3.1 Published 2020-03-10
Fix available
A fix is available. Upgrade to 9.0 / 16 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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 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.

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

A denial-of-service vulnerability in multiple Siemens SIMATIC industrial software products (OpenPCS 7, SIMATIC BATCH, SIMATIC NET PC Software, SIMATIC PCS 7, SIMATIC Route Control, SIMATIC WinCC) where specially crafted encrypted network messages can crash the affected service, causing system unavailability.

MitigationApply vendor-provided patches/updates to all affected product versions; if patches are unavailable, consider disabling encrypted communication as a temporary workaround and implement network segmentation to limit attack surface.

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
Openpcs 7Application
Affected:= 9.0= 9.0_update_1
Simatic BatchApplication
Affected:= 9.0
Simatic Net PcApplication
Affected:< 16= 16
Simatic Pcs 7Application
Affected:= 8.1= 8.2= 9.0
Simatic Route ControlApplication
Affected:< 9.0= 9.0
Simatic WinccApplication
Affected:= 7.4= 7.5= 7.5.1= 13= 14.0.1= 15.1= 16

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/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, look for Siemens SIMATIC software (OpenPCS 7, SIMATIC Batch, SIMATIC NET PC, SIMATIC PCS 7, SIMATIC Route Control, SIMATIC WinCC). Also check C:\Program Files\Siemens for product directories.
    Affected if Any of the affected products (OpenPCS 7, SIMATIC Batch, SIMATIC NET PC, SIMATIC PCS 7, SIMATIC Route Control, or SIMATIC WinCC) are listed in Programs and Features or exist in Siemens installation folders.
  2. Determine exact version of SIMATIC product
    Right-click the installed program in Programs and Features, select Properties, and view the Version field. Alternatively, locate the executable in the installation directory (commonly in C:\Program Files\Siemens\<ProductName>), right-click the main .exe, and select Properties > Details to view File Version.
    Affected if The version matches any of these: OpenPCS 7 (9.0, 9.0_update_1), SIMATIC Batch (9.0), SIMATIC NET PC (<16 or =16), SIMATIC PCS 7 (8.1, 8.2, 9.0), SIMATIC Route Control (<9.0 or =9.0), SIMATIC WinCC (7.4, 7.5, 7.5.1, 13, 14.0.1, 15.1, 16).
  3. Verify encrypted communication is enabled
    Open the SIMATIC product configuration or management console. For SIMATIC WinCC, check the WinCC Explorer > Computer properties > Parameters for communication settings. For SIMATIC NET PC, check the PC Station configuration. Look for SSL/TLS or encrypted channel settings.
    Affected if Encrypted network communication (SSL/TLS) is enabled in the product configuration, which is typically the default state for affected versions.

You are affected if any of the listed SIMATIC products are installed with a version matching the affected ranges AND encrypted communication is enabled (which is typically the default).

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
Upgrade available Upgrade to 9.0 / 16 or later
Fixed in 9.016
Interim mitigation

Apply vendor-provided patches/updates to all affected product versions; if patches are unavailable, consider disabling encrypted communication as a temporary workaround and implement network segmentation to limit attack surface.

Fix this in Openpcs 7 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-19282 — 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-2019-19282 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