Vulnerability in Siemens Simatic Wincc Sm At Rtclient (CVE-2017-6871)
Summary
Vulnerability in Siemens Simatic Wincc Sm At Rtclient (CVE-2017-6871). 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) and SIMATIC WinCC Sm@rtClient for Android Lite (All versions before V1.0.2.2). An attacker with physical access to an unlocked mobile device, that has the affected app running, could bypass the app's authentication mechanism under certain conditions.
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-6871 has been found in Siemens Simatic Wincc Sm At Rtclient.
Confidential information can be exposed externally. CVSS score: 5.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-6871" on the vendor's site.
CVE-2017-6871 (Siemens Simatic Wincc Sm At Rtclient) — CWE-288 / CVSS v3 5.4
Attack vector: physical / 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-288) exists in Siemens Simatic Wincc Sm At Rtclient.
Check the vendor advisory for the affected versions of Siemens Simatic Wincc Sm At Rtclient.
Severity: Medium (CVSS 5.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