CVE-2017-14031
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 Access Control issue was discovered in Trihedral VTScada 11.3.03 and prior. A local, non-administrator user has privileges to read and write to the file system of the target machine.
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 confidenceTrihedral VTScada 11.3.03 and prior runs with excessive privileges, allowing local non-administrator users to read and write to arbitrary file system locations on the target machine due to improper access control in the application.
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<= 11.3.03CVSS 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.0/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.
-
Identify VTScada installation and versionLocate the VTScada installation directory and check the application version (typically found in the program files folder, in version metadata or the application's About/Properties window)Affected if The installed version is 11.3.03 or any earlier version (anything <= 11.3.03)
-
Verify the VTScada service accountOpen Windows Services, locate the VTScada service, and check the 'Log on as' account configurationAffected if The service runs under a highly privileged account such as LocalSystem, Local Administrator, or a domain admin account rather than a restricted service account
-
Inspect file permissions on VTScada directoriesRight-click the VTScada installation folder, select Properties, then Security tab, and review which user groups have Read/Write permissionsAffected if Standard non-administrator users or 'Users' group have Full Control or Write permissions to the VTScada program directory or configuration folders
-
Test write access to protected locationsUsing a limited (non-admin) Windows account, attempt to create or modify files in system directories or VTScada program folders outside designated data areasAffected if A standard user account can successfully write files to locations that should be restricted to administrators only
-
Check for unnecessary user access rightsReview VTScada's internal user management or security configuration (if accessible through admin console) for grants of file system access to standard usersAffected if The application configuration grants file system access permissions to non-administrator user accounts beyond what is required for normal operation
You are affected if VTScada version is 11.3.03 or earlier AND the service runs with elevated privileges AND non-administrator users have excessive file system access rights.
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 dataApply vendor patch if available; otherwise, configure the VTScada service to run with least privilege by restricting file system permissions for the service account and ensuring the application does not grant unnecessary file access to standard users.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14031 — 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-14031 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