CVE-2017-10829
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 · uneditedUntrusted search path vulnerability in Remote Support Tool (Enkaku Support Tool) All versions distributed through the website till 2017 August 10 allow an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.
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 confidenceThe Enkaku Support Tool contains an untrusted search path vulnerability that allows the application to load DLLs from attacker-controlled directories. By placing a malicious DLL in an unspecified directory that the application searches, an attacker can achieve privilege escalation to execute code with elevated 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 dataall versionsCVSS 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 Enkaku Support Tool installationSearch the system for the Enkaku Support Tool executable or application files. Check common installation directories such as C:\Program Files\, C:\Program Files (x86)\, or the application's default installation path.Affected if The tool is found installed on the system. Since all versions are affected, any installation is potentially vulnerable.
-
Identify the application executable locationLocate the main executable file (typically named something like enkaku.exe or similar) and note its full path. Use file explorer search or command-line tools like 'where' or 'Get-ChildItem' to find it.Affected if The executable runs from a directory that is world-writable or accessible to unprivileged users, allowing an attacker to place a malicious DLL in that directory.
-
Check the system PATH for insecure directoriesOpen a command prompt and run 'echo %PATH%' to view the system PATH environment variable. Examine each directory in the PATH for world-writable permissions using 'icacls <directory>' or file explorer properties.Affected if The PATH contains directories with weak permissions (such as world-writable folders) where an attacker could place a malicious DLL that the application might load.
-
Examine the application directory for unexpected DLLsList all DLL files in the same directory as the Enkaku Support Tool executable. Use 'dir *.dll' or PowerShell 'Get-ChildItem *.dll' to enumerate existing DLLs. Compare against expected application DLLs if known.Affected if Unexpected or unknown DLL files exist in the application's directory that were not part of a clean installation, potentially indicating compromise.
-
Verify application execution contextCheck if the Enkaku Support Tool runs with elevated privileges. Review the application shortcut or executable properties for any 'Run as administrator' setting, and check associated services if it runs as a Windows service.Affected if The application executes with administrative or elevated privileges, which means a successful DLL hijacking attack would grant the attacker those elevated privileges.
A user is affected if the Enkaku Support Tool is installed on their system and runs from a directory or PATH that contains attacker-accessible locations where malicious DLLs could be placed and loaded.
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 a version of the Enkaku Support Tool released after August 10, 2017, which should contain the vendor patch. Alternatively, ensure the application runs from secure directories and remove world-writable directories from system PATH.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10829 — 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-10829 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