CVE-2017-2219
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 the [Simeji for Windows] installer (simeji.exe) 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 confidenceAn untrusted search path vulnerability in the Simeji for Windows installer (simeji.exe) allows the application to load malicious DLLs from attacker-controlled directories. When the installer executes, it searches for required DLLs in directories that may be writable by unprivileged users, enabling DLL planting and privilege escalation to the installer's 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= 1.0.0.7CVSS 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 Simeji installer versionLocate the simeji.exe installer file and check its version properties (right-click > Properties > Details) or use: Get-ItemProperty -Path "C:\path\to\simeji.exe" | Select-Object -ExpandProperty FileVersionAffected if Version is exactly 1.0.0.7
-
Check installed Simeji application versionLook for installed Simeji application in Add/Remove Programs or check: Get-ItemProperty "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*" | Where-Object {$_.DisplayName -like "*Simeji*"} | Select-Object DisplayName, DisplayVersionAffected if Installed version is exactly 1.0.0.7
-
Examine PATH for world-writable directoriesRun: $env:PATH -split ';' | ForEach-Object { if ((Test-Path $_) -and (Get-Acl $_).Access | Where-Object {$_.IdentityReference -like "*Everyone*" -or $_.IdentityReference -like "*Users*" -and $_.FileSystemRights -like "*Write*"}) { $_ } }Affected if Any directory in PATH is writable by unprivileged users (Everyone, Users group with Write permissions)
-
Verify DLL search order vulnerabilityMonitor the installer using Process Monitor (ProcMon) from Sysinternals - set filter for Process Name = simeji.exe and Operation = Load Image, then run the installer and check if it loads DLLs from PATH directories rather than its own application directoryAffected if Installer loads DLLs from directories in PATH that precede the application directory in the search order
You are affected if you have Baidu Simeji version 1.0.0.7 installed or as an installer, AND your PATH contains writable directories from which the installer could load 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 dataReplace the installer with a version that implements secure DLL search path order (starting with the application directory) and uses explicit absolute paths or manifests to specify trusted DLL locations. Verify the fix by testing the installer in environments with untrusted directories present in the PATH.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2219 — 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-2219 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