CVE-2017-2684
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 · uneditedSiemens SIMATIC Logon prior to V1.5 SP3 Update 2 could allow an attacker with knowledge of a valid user name, and physical or network access to the affected system, to bypass the application-level authentication.
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 · high confidenceSiemens SIMATIC Logon prior to V1.5 SP3 Update 2 contains an authentication bypass vulnerability where an attacker with knowledge of a valid username and physical or network access can bypass application-level authentication mechanisms, potentially gaining unauthorized access to the industrial control system.
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.5CVSS 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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
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.
-
Confirm SIMATIC Logon installationOpen Windows Control Panel > Programs and Features, or check registry key HKLM\SOFTWARE\Siemens\SIMATIC Logon for existenceAffected if SIMATIC Logon is found installed on the system
-
Identify installed versionCheck registry key HKLM\SOFTWARE\Siemens\SIMATIC Logon\Version, or right-click the SIMATIC Logon executable in the installation folder and view Properties > DetailsAffected if Version is 1.5 or lower (including all 1.x versions before V1.5 SP3 Update 2)
-
Verify authentication module is activeCheck if SIMATIC Logon service is running (services.msc) and if the Logon GUI is accessible on the network or locallyAffected if The SIMATIC Logon authentication interface is accessible and waiting for user credentials
-
Check for network exposureReview Windows Firewall rules and network listening ports for SIMATIC Logon (typically port 16300 or as configured), and verify network segment access controlsAffected if SIMATIC Logon port is exposed to network segments accessible by untrusted users
You are affected if SIMATIC Logon version 1.5 or lower is installed and its authentication service is active, allowing a user with valid credentials and network access to potentially bypass the login mechanism.
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.
dbcve · scopedUpdate Siemens SIMATIC Logon to version V1.5 SP3 Update 2 or later to remediate the authentication bypass vulnerability.
V1.5 SP3 Update 2
- 1. Identify the currently installed version of Siemens SIMATIC Logon
- 2. Obtain Siemens SIMATIC Logon V1.5 SP3 Update 2 or later from official Siemens sources
- 3. Apply the update following Siemens installation documentation
- 4. Verify the installation completed successfully
- 5. Test that authentication is functioning correctly with the patch applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2684 — 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-2684 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