CVE-2017-10826
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 Security Kinou Mihariban v1.0.21 and earlier 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 confidenceThis is a DLL hijacking vulnerability (untrusted search path) in Security Kinou Mihariban v1.0.21 and earlier. The application loads DLLs from directories that are not secured, allowing an attacker to place a malicious DLL that gets loaded with the application's privileges, resulting in privilege escalation.
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<= 1.0.21CVSS 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.
-
Identify if Security Kinou Mihariban is installedCheck for the application in typical installation directories such as C:\Program Files\SecurityKinouMihariban or C:\Program Files (x86)\SecurityKinouMihariban, or look for the executable in the system's application listingAffected if The application is found with version 1.0.21 or earlier
-
Confirm the installed version numberRight-click the application executable, select Properties, and verify the File Version under the Details tab, or check Add/Remove Programs for the version informationAffected if The version is 1.0.21 or lower
-
Examine the DLL search path used by the applicationRun the application with a debugging tool or process monitor (such as Process Monitor from Sysinternals) to capture DLL load attempts and identify which directories the application searches for DLLsAffected if The application loads DLLs from user-writable directories such as the application directory, temp folders, or directories with weak permissions
-
Check permissions on directories in the DLL search pathUse icacls or file explorer to check which users have Write or Modify permissions on directories where the application loads DLLs fromAffected if Any directory in the DLL search path grants Write or Modify permissions to non-privileged users, allowing them to place a malicious DLL
-
Identify specific DLLs loaded from untrusted pathsUsing Process Monitor, filter for DLL load events by the application process and note the paths from which DLLs are being loadedAffected if The application loads any DLL from a directory that is writable by standard users
A user is affected if Security Kinou Mihariban version 1.0.21 or earlier is installed and the application loads DLLs from directories accessible to standard users, enabling an attacker to place a malicious DLL for privilege escalation.
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 dataRemediate by ensuring the application loads DLLs only from secure, trusted locations using explicit paths or secure DLL search order, and by validating all loaded DLLs before execution.
- Consultation4.0 h
- Implementation12.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10826 — 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-10826 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