Skip to content
Fencer Intel
medium 5.5

CVE-2019-10917 json

A vulnerability has been identified in SIMATIC PCS 7 V8.0 and earlier (All versions), SIMATIC PCS 7 V8.1 (All versions < V8.1 with WinCC V7…

published 7y ago modified 4mo ago also EUVD-2019-2631

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 18%
public exploits
0
none known

Summary

A vulnerability has been identified in SIMATIC PCS 7 V8.0 and earlier (All versions), SIMATIC PCS 7 V8.1 (All versions < V8.1 with WinCC V7.3 Upd 19), SIMATIC PCS 7 V8.2 (All versions < V8.2 SP1 with WinCC V7.4 SP1 Upd11), SIMATIC PCS 7 V9.0 (All versions < V9.0 SP2 with WinCC V7.4 SP1 Upd11), SIMATIC WinCC (TIA Portal) V13 (All versions), SIMATIC WinCC (TIA Portal) V14 (All versions < V14 SP1 Upd 9), SIMATIC WinCC (TIA Portal) V15 (All versions < V15.1 Upd 3), SIMATIC WinCC Runtime Professional V13 (All versions), SIMATIC WinCC Runtime Professional V14 (All versions < V14.1 Upd 8), SIMATIC WinCC Runtime Professional V15 (All versions < V15.1 Upd 3), SIMATIC WinCC V7.2 and earlier (All versions), SIMATIC WinCC V7.3 (All versions < V7.3 Upd 19), SIMATIC WinCC V7.4 (All versions < V7.4 SP1 Upd 11), SIMATIC WinCC V7.5 (All versions < V7.5 Upd 3). An attacker with local access to the project file could cause a Denial-of-Service condition on the affected product while the project file is loaded. Successful exploitation requires access to the project file. An attacker could use the vulnerability to compromise availability of the affected system. At the time of advisory publication no public exploitation of this security vulnerability was known.

Is CVE-2019-10917 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-19-134-08 updated cvss 3.3

ICSA-19-134-08 Siemens SIMATIC PCS7, WinCC, TIA Portal (Update D)

  • Siemens SIMATIC PCS 7 V8.0 and earlier
    affected: mitigation
  • Siemens SIMATIC PCS 7 V8.1 <V8.1_with_WinCC_V7.3_Upd_19
    affected: fixed in V7.3, mitigation support.industry.siemens.com
  • Siemens SIMATIC PCS 7 V8.2 <V8.2_SP1_with_WinCC_V7.4_SP1_Upd11 Siemens SIMATIC PCS 7 V9.0 <V9.0_SP2_with_WinCC_V7.4_SP1_Upd11
    affected: fixed in V7.4, mitigation support.industry.siemens.com
  • Siemens SIMATIC WinCC (TIA Portal) V13
    affected: mitigation
  • Siemens SIMATIC WinCC (TIA Portal) V14 <V14_SP1_Upd_9
    affected: fixed in V14, mitigation support.industry.siemens.com
  • Siemens SIMATIC WinCC (TIA Portal) V15 <V15.1_Upd_3
    affected: fixed in V15.1, mitigation support.industry.siemens.com
  • Siemens SIMATIC WinCC Runtime Professional V13
    affected: mitigation
  • Siemens SIMATIC WinCC Runtime Professional V14 <V14.1_Upd_8
    affected: fixed in V14.1, mitigation support.industry.siemens.com
show 5 more

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:N/A:P

Affected products

  • Siemens AG SIMATIC PCS 7 V8.0 and earlier
  • Siemens AG SIMATIC PCS 7 V8.1
  • Siemens AG SIMATIC PCS 7 V8.2
  • Siemens AG SIMATIC PCS 7 V9.0
  • Siemens AG SIMATIC WinCC (TIA Portal) V13
  • Siemens AG SIMATIC WinCC (TIA Portal) V14
  • Siemens AG SIMATIC WinCC (TIA Portal) V15
  • Siemens AG SIMATIC WinCC Runtime Professional V13
  • Siemens AG SIMATIC WinCC Runtime Professional V14
  • Siemens AG SIMATIC WinCC Runtime Professional V15
  • Siemens AG SIMATIC WinCC V7.2 and earlier
  • Siemens AG SIMATIC WinCC V7.3
  • Siemens AG SIMATIC WinCC V7.4
  • Siemens AG SIMATIC WinCC V7.5

Classification

Weakness
  • CWE-248 Uncaught Exception
  • CWE-755 Improper Handling of Exceptional Conditions

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.