CVE-2017-14029
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 Uncontrolled Search Path Element issue was discovered in Trihedral VTScada 11.3.03 and prior. The program will execute specially crafted malicious dll files placed on 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 confidenceThis is a DLL hijacking (uncontrolled search path element) vulnerability in Trihedral VTScada 11.3.03 and prior. The application loads DLL files using insecure search paths, allowing attackers to place malicious DLLs in directories that the application searches (such as the current working directory or system paths). When the application runs, it inadvertently loads and executes the attacker's DLL instead of the legitimate one, achieving code execution in the context of the vulnerable 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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.
-
Verify if Trihedral VTScada is installedLook for VTScada in the Windows installed programs list (Control Panel > Programs and Features) or check common installation directories such as C:\Program Files\Trihedral or C:\Program Files (x86)\TrihedralAffected if VTScada is found on the system
-
Determine the installed VTScada versionRight-click on the main VTScada executable (commonly vtScada.exe or similar) in the installation directory, select Properties, and view the Details tab for the Product Version. Alternatively, check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Trihedral or HKEY_CURRENT_USER\SOFTWARE\Trihedral for version informationAffected if The version displayed is 11.3.03 or lower
-
Compare version against affected rangeCompare the installed version number to the affected range: any version less than or equal to 11.3.03 is vulnerable. Version 11.3.04 and later are not affectedAffected if The installed version is 11.3.03 or any prior version (e.g., 11.3.00, 11.2.x, earlier releases)
-
Confirm the application uses insecure DLL search pathsInspect the application's DLL loading behavior using process monitoring tools (such as Process Monitor from Sysinternals) to observe which directories the application searches when loading DLLs. Look for DLL loads from the current working directory or system paths without using SetDllDirectoryAffected if The application loads DLLs from directories controllable by an attacker (current directory or unwritable system paths)
A system is affected if Trihedral VTScada version 11.3.03 or lower is installed and the application loads DLLs from insecure search paths, allowing potential DLL hijacking by placing malicious DLLs in directories the application searches.
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 dataFix the application code to use fully qualified explicit paths for all DLL loads, enable safe DLL search mode (SetDllDirectory), and implement DLL signature verification/whitelisting to ensure only trusted DLLs are loaded.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14029 — 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-14029 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