CVE-2017-6871
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAuthentication bypass vulnerability in SIMATIC WinCC Sm@rtClient for Android (both regular and Lite versions before V1.0.2.2) allows an attacker with physical access to an unlocked mobile device running the affected application to bypass the app's authentication mechanism under certain conditions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.0.2.1<= 1.0.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if SIMATIC WinCC Sm@rtClient is installedOpen Android Settings > Apps > Applications Manager and look for SIMATIC WinCC Sm@rtClient or SIMATIC WinCC Sm@rtClient Lite in the app listAffected if Either the regular or Lite version of the app is present on the device
-
Determine the installed app versionIn Android Settings > Apps > SIMATIC WinCC Sm@rtClient (or Lite), scroll to the App info screen and note the version number displayed under the app nameAffected if The version shown is 1.0.2.1 or earlier (any version <= 1.0.2.1)
-
Check if the app has authentication configuredLaunch the SIMATIC WinCC Sm@rtClient app and observe whether a password or PIN prompt appears on startup, or check if authentication settings are accessible in the app's settings menuAffected if The app has password/PIN protection enabled and the device can be left unattended or unlocked
-
Verify the physical access scenarioAssess whether the Android device running the app is used in environments where it could be left unlocked and unattended (factory floor, public areas, shared workstations)Affected if The device is or could be left unlocked in accessible locations where unauthorized physical access is possible
You are affected if SIMATIC WinCC Sm@rtClient (or Lite) for Android is installed at version 1.0.2.1 or earlier and the device can be accessed while unlocked.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate SIMATIC WinCC Sm@rtClient for Android and Android Lite to version V1.0.2.2 or later to remediate this authentication bypass vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6871 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-6871 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data