CVE-2017-12717
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 Advantech WebAccess versions prior to V8.2_20170817. A maliciously crafted dll file placed earlier in the search path may allow an attacker to execute code within the context of the application.
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 confidenceAdvantech WebAccess versions prior to V8.2_20170817 are vulnerable to DLL hijacking due to an uncontrolled search path element. The application loads DLL files without specifying full paths, allowing an attacker to place a maliciously crafted DLL earlier in the search path (such as the application directory) which will be loaded instead of the legitimate DLL, executing code within the application context.
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<= 8.2CVSS 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.
-
Confirm WebAccess installationCheck if Advantech WebAccess is installed on the system by looking for the application in program files or the Windows registry under HKLM\SOFTWARE\Advantech\WebAccessAffected if The application is installed on the system
-
Identify installed versionLocate the WebAccess version information, typically found in the application directory, in the Windows registry, or by checking the executable file properties of the main WebAccess componentAffected if The version is 8.2 or earlier, or any version prior to V8.2_20170817
-
Inspect application directory for unauthorized DLLsExamine the main WebAccess installation directory for any unexpected or suspicious DLL files that are not part of the standard installation, particularly DLLs that may have been placed there by an attackerAffected if Unexpected DLL files exist in the application directory that are not part of the legitimate installation
-
Review DLL search path orderCheck the system PATH environment variable and any application-specific PATH configurations to identify which directories are searched when the application loads DLL files, and determine if any non-system directories appear earlier in the search orderAffected if User-writable directories are present earlier in the DLL search path than system directories
-
Verify directory permissionsReview write permissions on the WebAccess application directory and all directories earlier in the DLL search path to determine if an unprivileged user could place a malicious DLL fileAffected if Non-admin users have write access to directories in the DLL search path that precede system directories
The environment is affected if WebAccess version is 8.2 or earlier and any unauthorized or suspicious DLL files exist in the application directory or any writable directory earlier in the DLL search path.
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 to WebAccess V8.2_20170817 or later. As a temporary mitigation, ensure no unauthorized DLL files exist in the application directory or directories earlier in the search path, and restrict write access to those locations.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12717 — 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-12717 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