Skip to content
Fencer Intel
critical 10.0

CVE-2014-8551 json

The WinCC server in Siemens SIMATIC WinCC 7.0 through SP3, 7.2 before Update 9, and 7.3 before Update 2; SIMATIC PCS 7 7.1 through SP4, 8.0…

published 11y ago modified 4mo ago also EUVD-2014-8388

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.3%
EPSS 5.3% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

The WinCC server in Siemens SIMATIC WinCC 7.0 through SP3, 7.2 before Update 9, and 7.3 before Update 2; SIMATIC PCS 7 7.1 through SP4, 8.0 through SP2, and 8.1; and TIA Portal 13 before Update 6 allows remote attackers to execute arbitrary code via crafted packets.

Is CVE-2014-8551 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-14-329-02D updated cvss 10.0

Siemens SIMATIC WinCC, PCS7, and TIA Portal Vulnerabilities

  • Siemens SIMATIC PCS 7 V7.1 SP4 and prior Siemens SIMATIC PCS 7 V8.0 <V8.0_SP2_with_WinCC_V7.2_Update_9 Siemens SIMATIC PCS 7 V8.1 <with_WinCC_V7.3_Update_2 Siemens SIMATIC WinCC V7.2 <V7.2_Update_9 Siemens SIMATIC WinCC V7.0 SP3 and prior Siemens SIMATIC WinCC V7.3 <V7.3_Update_2
    +1 more products
    Siemens TIA Portal V13 (including WinCC Professional Runtime) <V13_Update_6
    affected: mitigation “WinCC 7.0 Upgrade to WinCC 7.0 SP2 Update 11: (http://support.automation.siemens.com/WW/view/en/107174184)”

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

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.