CVE-2014-1698 json
Directory traversal vulnerability in Siemens SIMATIC WinCC OA before 3.12 P002 January allows remote attackers to read arbitrary files via…
published 2014-02-07 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-1772
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
Directory traversal vulnerability in Siemens SIMATIC WinCC OA before 3.12 P002 January allows remote attackers to read arbitrary files via crafted packets to TCP port 4999.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-14-035-01 updated cvss 5.0
Siemens SIMATIC WinCC OA Multiple Vulnerabilities
-
Siemens SIMATIC WinCC OA <3.12_P002affected: mitigation “Siemens recommends updating to SIMATIC WinCC OA v3.12 and to install patch P002 January”
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
3.51% chance of exploitation in the next 30 days, higher than 89% 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-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
siemens.com
/innovation/pool/de/forschungsfelder/siemens_security_advisory_ssa-342587.pdf
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/90935
vdb-entry
-
secunia.com
/advisories/56651
third-party-advisory
-
securityfocus.com
/bid/65349
vdb-entry
-
ics-cert.us-cert.gov
/advisories/ICSA-14-035-01
us-government-resource
-
osvdb.org
/102811
vdb-entry
Sources
- CVE List CVE-2014-1698
- NVD CVE-2014-1698
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.