Vulnerability in Siemens Simatic Wincc Sm At Rtclient (CVE-2017-6870)
Summary
Vulnerability in Siemens Simatic Wincc Sm At Rtclient (CVE-2017-6870). Confidential information can be exposed externally.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2017-6870 has been found in Siemens Simatic Wincc Sm At Rtclient.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Siemens Simatic Wincc Sm At Rtclient CVE-2017-6870" on the vendor's site.
CVE-2017-6870 (Siemens Simatic Wincc Sm At Rtclient) — CWE-300 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-300) exists in Siemens Simatic Wincc Sm At Rtclient.
Check the vendor advisory for the affected versions of Siemens Simatic Wincc Sm At Rtclient.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Siemens Simatic Wincc Sm At Rtclient を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory securityfocus.com
- patch siemens.com