dbcve.org
Simatic Et 200sp Open Controller Cpu 1515sp Pc FirmwareOperating system · Siemens

CVE-2019-10943

HIGH · 7.5 CVSS v3.1 Published 2019-08-13
Fix available
A fix is available. Upgrade to 2.8.1 / 4.4 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 SIMATIC Drive Controller family (All versions), SIMATIC ET 200SP Open Controller CPU 1515SP PC (incl. SIPLUS variants) (All versions), SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants) (All versions < V20.8), SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants) (All versions >= V20.8), SIMATIC S7-1200 CPU family (incl. SIPLUS variants) (All versions < V4.4.0), SIMATIC S7-1200 CPU family (incl. SIPLUS variants) (All versions >= V4.4.0), SIMATIC S7-1500 CPU family (incl. related ET200 CPUs and SIPLUS variants) (All versions < V2.8.1), SIMATIC S7-1500 CPU family (incl. related ET200 CPUs and SIPLUS variants) (All versions >= V2.8.1), SIMATIC S7-1500 Software Controller (All versions < V20.8), SIMATIC S7-1500 Software Controller (All versions >= V20.8), SIMATIC S7-PLCSIM Advanced (All versions < V3.0), SIMATIC S7-PLCSIM Advanced (All versions >= V3.0). An attacker with network access to port 102/tcp could potentially modify the user program on the PLC in a way that the running code is different from the source code which is stored on the device. An attacker must have network access to affected devices and must be able to perform changes to the user program. The vulnerability could impact the perceived integrity of the user program stored on the CPU. An engineer that tries to obtain the code of the user program running on the device, can receive different source code that is not actually running on the device.

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

This vulnerability in Siemens SIMATIC PLCs (S7-1200, S7-1500, ET200SP, Drive Controller, S7-PLCSIM Advanced) allows an attacker with network access to port 102/tcp to modify user program code on the PLC such that the running code differs from the source code stored on the device. This creates an integrity violation where the actual PLC behavior does not match what an engineer would expect based on the stored program, enabling deceptive manipulation of industrial processes.

MitigationRestrict network access to port 102/tcp via firewalls or network segmentation, implement industrial DMZ, and monitor for unauthorized program modifications; verify program integrity through trusted offline backups and hash comparisons.

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
Simatic Et 200sp Open Controller Cpu 1515sp Pc FirmwareOperating system
Affected:all versions
Simatic Et 200sp Open Controller Cpu 1515sp Pc2 FirmwareOperating system
Affected:< 20.8
Simatic S7 1200 Cpu 1211c FirmwareOperating system
Affected:< 4.4
Simatic S7 1200 Cpu 1212c FirmwareOperating system
Affected:< 4.4
Simatic S7 1200 Cpu 1214c FirmwareOperating system
Affected:< 4.4
Simatic S7 1200 Cpu 1215c FirmwareOperating system
Affected:< 4.4
Simatic S7 1200 Cpu 1217c FirmwareOperating system
Affected:< 4.4
Simatic S7 1500 Cpu 1518 FirmwareOperating system
Affected:< 2.8.1

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
High
Availability
None

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

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 PLC model
    Locate the specific SIMATIC PLC model (S7-1200, S7-1500, ET200SP Open Controller, or S7-PLCSIM Advanced) in your environment. Consult device documentation, TIA Portal project files, or physically inspect the PLC hardware labeling.
    Affected if The model is one of: ET200SP Open Controller CPU 1515SP PC or PC2, S7-1200 CPU 1211C/1212C/1214C/1215C/1217C, or S7-1500 CPU 1518.
  2. Check firmware version
    Access the PLC via TIA Portal or web interface, or use PLC programming software to read the firmware version. Compare against the affected version thresholds: ET200SP PC2 < 20.8, S7-1200 (all listed models) < 4.4, S7-1500 CPU 1518 < 2.8.1.
    Affected if The installed firmware version is lower than the fixed version for your specific model.
  3. Verify port 102 accessibility
    Perform a network scan from untrusted segments (or use netstat/ss on adjacent hosts) to determine if port 102/tcp is listening and reachable from any network zone that contains untrusted or external systems.
    Affected if Port 102/tcp is exposed to networks outside the trusted engineering workstation zone.
  4. Compare program integrity
    In TIA Portal, use the Compare function or retrieve the program blocks from the PLC and compare them byte-for-byte against the known-good offline project file. Check for unexpected changes in logic, additional blocks, or modified code.
    Affected if The program code currently running on or stored in the PLC differs from your trusted offline backup.

You are affected if you have an affected PLC model with vulnerable firmware AND port 102/tcp is reachable from an untrusted network, regardless of whether program integrity has been altered yet.

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 2.8.1 / 4.4 / 20.8 or later
Fixed in 2.8.14.420.8
Interim mitigation

Restrict network access to port 102/tcp via firewalls or network segmentation, implement industrial DMZ, and monitor for unauthorized program modifications; verify program integrity through trusted offline backups and hash comparisons.

Fix this in Simatic Et 200sp Open Controller Cpu 1515sp Pc Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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