CVE-2017-10828
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 Flets Install Tool all versions distributed through the website till 2017 August 8 allows 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 · moderate confidenceUntrusted search path vulnerability in Flets Install Tool allows DLL hijacking. An attacker can place a malicious Trojan horse DLL in an unspecified directory that the application searches when loading libraries, causing the application to execute the attacker's code with the privileges of the affected 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= 12.6.0CVSS 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.
-
Locate Ntt Flets Install Tool installation directorySearch for 'Flets Install Tool' or 'NTT Flets' in Program Files directories, or check common installation paths like C:\Program Files\Ntt or C:\Program Files (x86)\Ntt. Also search the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Flets'.Affected if The application is found installed on the system
-
Verify installed version is 12.6.0Check the version property of the executable, typically named something like 'FletsInstallTool.exe' or similar within the installation directory. Right-click the executable, select Properties, and view the Details tab for File Version, or use PowerShell: Get-Item 'C:\Path\To\FletsInstallTool.exe' | Select-Object VersionInfoAffected if The installed version is exactly 12.6.0 (this specific version is affected)
-
Identify DLL search path behaviorRun the application with process monitoring (like Process Monitor from Sysinternals) to observe DLL loading behavior. Look for the application attempting to load DLLs from directories outside its installation folder, particularly user-writable locations or the application directory.Affected if The application loads DLLs from directories other than its own installation directory, or from locations where an unprivileged user could place a malicious DLL
A system is affected only if Ntt Flets Install Tool version 12.6.0 is installed and its DLL search path allows loading from untrusted directories where an attacker could place malicious DLLs.
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 dataModify the application to use secure DLL loading by specifying full paths for DLL dependencies and removing vulnerable directories from the search order, or ensure all required DLLs are located in the application's secure directory.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10828 — 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-10828 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