CVE-2017-10827
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 Azukeru for Windows Auto Backup Tool v1.0.3.0 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 · moderate confidenceThis is a DLL hijacking vulnerability where the Flets Azukeru for Windows Auto Backup Tool loads DLLs from untrusted search paths, allowing an attacker to place a malicious Trojan horse DLL in a directory that gets searched by the application. When the application runs with elevated privileges, the attacker can execute arbitrary code with those 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<= 1.0.3.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.
-
Verify if Flets Azukeru Auto Backup Tool is installedCheck the system for the presence of the application by searching for 'Flets Azukeru' or 'Azukuu' in Program Files, Program Files (x86), or the application's typical installation directory. Look for executable files related to the backup tool.Affected if The application is found installed on the system.
-
Determine the installed versionRight-click the application's executable file, select Properties, and check the 'File version' or 'Product version' field in the Details tab. Alternatively, open the application and check Help > About for version information.Affected if The version is 1.0.3.0 or lower.
-
Check if the application runs with elevated privilegesRight-click the application's shortcut or executable, select Properties, then go to the Compatibility tab and check if 'Run this program as administrator' is selected. Also check if the application is configured to run via a scheduled task with elevated privileges.Affected if The application is configured to run with administrator privileges or elevated rights.
-
Inspect the application directory for writable locationsCheck the permissions on the application's installation directory to determine if standard users can write files to that location. Use icacls or File Explorer security properties to review write permissions for non-admin users.Affected if Non-privileged users can write files to the application directory or any directory in its DLL search path.
The system is affected if the Flets Azukeru Auto Backup Tool version 1.0.3.0 or lower is installed and runs with elevated privileges, allowing untrusted DLL loading.
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 implementing secure DLL search order (removing current directory from search path), using absolute paths for all DLL loads, or embedding required DLLs within the application binary, and verify no vulnerable DLL loading behavior remains.
- Consultation3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10827 — 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-10827 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