CVE-2017-12728
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 · uneditedAn Improper Privilege Management issue was discovered in SpiderControl SCADA Web Server Version 2.02.0007 and prior. Authenticated, non-administrative local users are able to alter service executables with escalated privileges, which could allow an attacker to execute arbitrary code under the context of the current system services.
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 confidenceSpiderControl SCADA Web Server versions 2.02.0007 and prior contain an improper privilege management vulnerability where authenticated non-administrative local users can modify service executables, enabling arbitrary code execution with elevated system service privileges.
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<= 2.02.0007CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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.
-
Check if SpiderControl SCADA Web Server is installedOpen Windows Services (services.msc) and look for a service named 'SpiderControl' or 'ScadaWebServer' or check Program Files for a SpiderControl directory. Alternatively, run 'wmic product get name,version' to list installed software.Affected if No SpiderControl SCADA Web Server service or software is found on the system.
-
Determine the installed versionIf found, check the version of the SpiderControl SCADA Web Server installation. Right-click the service > Properties to see the path to the executable, then right-click the executable > Properties > Details to view the version. Or check the registry under HKLM\SOFTWARE\SpiderControl or the uninstall entry in the registry.Affected if The installed version is 2.02.0007 or any version prior to this.
-
Verify non-administrative user write access to service executablesLocate the SCADA Web Server service executable (from the service Properties path). Right-click the executable file > Properties > Security tab > Permissions. Check if Users or Authenticated Users group has Write or Modify permissions to the executable file.Affected if Non-administrative users (Users group, Authenticated Users, or specific non-admin users) have Write or Modify permissions on the service executable.
-
Check the service account configurationOpen Services, find the SpiderControl service, right-click > Properties > Log On tab. Verify which account the service runs under (Local System, Local Service, or a specific user account).Affected if The service runs under Local System, Local Service, or another privileged account, and non-admin users have write access to the executable.
-
Confirm local user authentication is enabledCheck the SpiderControl web server configuration files (typically in the installation directory, look for config.xml, users.xml, or similar) to determine if local user accounts are enabled for authentication.Affected if Local user authentication is enabled and non-admin local users exist on the system.
A user is affected if SpiderControl SCADA Web Server version 2.02.0007 or prior is installed, the service runs with elevated privileges, and non-administrative local users have write permissions to the service executable with local authentication enabled.
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 dataRestrict write permissions on SCADA service executables to administrator accounts only, and apply vendor patch when available. Verify service account has minimal necessary privileges.
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12728 — 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-12728 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