A vulnerability has been identified in SIMATIC WinCC OA Operator iOS App (All versions < V1.4).

published 2018-04-23 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-16633

cvss: 4.6; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits: 0; none known

A vulnerability has been identified in SIMATIC WinCC OA Operator iOS App (All versions < V1.4). Insufficient protection of sensitive information (e.g. session key for accessing server) in Siemens WinCC OA Operator iOS app could allow an attacker with physical access to the mobile device to read unencrypted data from the app's directory. Siemens provides mitigations to resolve the security issue.

Vendor advisories

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

cisa ICSA-18-109-01 updated 2018-10-09 cvss 4.0

Siemens SIMATIC WinCC OA Operator IOS App (Update A)

Siemens SIMATIC WinCC OA Operator iOS App < 1.4
affected: mitigation “Siemens has recommended that users update to v1.4, which can be located here:” itunes.apple.com

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

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected products

Siemens AG SIMATIC WinCC OA Operator iOS App

Classification

Weakness

CWE-538 Insertion of Sensitive Information into Externally-Accessible File or Directory
CWE-311 Missing Encryption of Sensitive Data

References

cert-portal.siemens.com /productcert/pdf/ssa-597741.pdf
vendor-advisory
securityfocus.com /bid/103941
vdb-entry, third-party-advisory

Sources

CVE List CVE-2018-4847
NVD CVE-2018-4847

Fencer Vulns 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.

Summary