CVE-2018-0517
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 Anshin net security for Windows Version 16.0.1.44 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 an untrusted search path (DLL hijacking) vulnerability in Anshin net security for Windows. The application loads DLLs from directories that are under user control, allowing an attacker to place a malicious DLL (Trojan horse) in an unspecified directory that the application searches when starting. When the application runs, it loads the attacker's DLL instead of the legitimate one, potentially executing 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 data<= 6.0.1.44CVSS 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.
-
Check if Anshin Net Security is installedOpen Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programsAffected if Kddi Anshin Net Security or Anshin Net Security appears in the installed programs list
-
Determine the installed versionRight-click the application executable (typically in C:\Program Files\KDAI or C:\Program Files (x86)\KDAI) and select Properties, or use 'Get-ItemProperty' on the installation directory to find the version informationAffected if The displayed version number is 6.0.1.44 or lower
-
Identify the application executable locationLocate the main executable file for Anshin Net Security, commonly named something like 'anshin.exe' or 'anshinGuard.exe' in the Program Files directoryAffected if The executable exists and is from the affected product range
-
Inspect the DLL search path behaviorUse a tool like Process Monitor (ProcMon) from Sysinternals to trace DLL loading when the application starts, filtering by the process name. Look for DLL loads from user-writable directories such as the application directory, current working directory, or PATH locationsAffected if The process attempts to load DLLs from directories outside the secure Windows system folders (System32, WinSxS)
-
Verify the PATH environment variableCheck the system and user PATH variables by running 'echo $env:PATH' in PowerShell or viewing System Properties > Environment Variables. Look for any directories that are writable by non-admin usersAffected if The PATH contains directories that allow unprivileged users to place files, creating a hijacking opportunity
If Kddi Anshin Net Security version 6.0.1.44 or lower is installed and the application loads DLLs from user-controlled directories, the environment is vulnerable to CVE-2018-0517.
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 dataUpgrade to a version newer than 16.0.1.44. If upgrading is not immediately possible, review and remove unsafe directories from the application's DLL search path, and ensure the application uses secure DLL loading practices (full paths, safe search order).
- 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-2018-0517 — 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-2018-0517 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