CVE-2014-8552 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 2014-11-26 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-8389
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- 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 read arbitrary files via crafted packets.
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 7.8
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_2affected: mitigation “WinCC 7.0 Upgrade to WinCC 7.0 SP2 Update 11: (http://support.automation.siemens.com/WW/view/en/107174184)”
+1 more productsfewer
Siemens TIA Portal V13 (including WinCC Professional Runtime) <V13_Update_6
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
2.05% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
Sources
- CVE List CVE-2014-8552
- NVD CVE-2014-8552
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.