CVE-2017-6870

CVE-2017-6870 is a high-severity vulnerability in Siemens Simatic Wincc Sm@rtclient with a CVSS 3.x base score of 7.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-300.

Key facts

Description

A vulnerability was discovered in Siemens SIMATIC WinCC Sm@rtClient for Android (All versions before V1.0.2.2). The existing TLS protocol implementation could allow an attacker to read and modify data within a TLS session while performing a Man-in-the-Middle (MitM) attack.

Frequently asked questions

What is CVE-2017-6870?
A vulnerability was discovered in Siemens SIMATIC WinCC Sm@rtClient for Android (All versions before V1.0.2.2). The existing TLS protocol implementation could allow an attacker to read and modify data within a TLS session while performing a Man-in-the-Middle (MitM) attack.
How severe is CVE-2017-6870?
CVE-2017-6870 has a CVSS 3.x base score of 7.4, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2017-6870 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (57th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-6870?
CVE-2017-6870 affects Siemens Simatic Wincc Sm@rtclient. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-6870?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-6870 published?
CVE-2017-6870 was published on 2017-08-08 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Siemens Simatic Wincc Sm@rtclient

All CVEs affecting Siemens Simatic Wincc Sm@rtclient →

Other CWE-300 vulnerabilities

Browse all CWE-300 vulnerabilities →