CVE-2017-10859
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 "i-filter 6.0 installer" timestamp of code signing is before 23 Aug 2017 (JST) 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 · high confidenceUntrusted search path vulnerability in i-filter 6.0 installer (code signed before 23 Aug 2017 JST) allows DLL hijacking. An attacker can place a malicious Trojan horse DLL in an unspecified directory that the installer searches for DLLs, causing it to be loaded 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 data= 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 the i-filter installer on the systemSearch for installer files matching patterns like 'ifilter*setup*.exe', 'ifilter*installer*.exe', or 'daj*ifilter*.exe' in common download and program directories. Check paths such as %USERPROFILE%\Downloads, %TEMP%, C:\Program Files\, or custom installation directories.Affected if The installer executable for version 6.0 is found on the system and was code signed before 23 August 2017.
-
Verify the digital signature timestampRight-click the installer executable, select Properties, then go to the Digital Signatures tab. Select the signature and click Details to view the 'Signed time' or 'Timestamp' field. Alternatively, use signtool.exe: signtool verify /pa /v "<installer_path>"Affected if The signature timestamp date is before 23 August 2017, indicating the vulnerable version.
-
Check file metadata for creation or modification datesRight-click the installer file, select Properties, and examine the Created date in the General tab. Also check the Details tab for version information indicating build date prior to August 2017.Affected if The file creation or build timestamp predates August 2017, suggesting the unpatched installer.
-
Determine where the installer is run fromReview the directory location from Step 1. Check if the installer resides in a shared network folder, external USB drive, or a directory with weak permissions where unprivileged users can write files.Affected if The installer is run from a directory where untrusted users can place malicious DLL files, enabling the hijacking attack.
A user is affected if the Daj I Filter Installer version 6.0 exists on their system with a code signing timestamp before 23 August 2017, or if the installer is executed from a directory writable by untrusted users.
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 dataObtain and use an updated version of the i-filter 6.0 installer with a code signing timestamp after 23 August 2017, which should contain the vendor fix for secure DLL loading. Avoid running the installer in untrusted or shared directory locations.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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,768.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10859 — 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-10859 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