CVE-2017-2215
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 Installer of "Setup file of advance preparation" (jizen_setup.exe) (The version which was available on the website prior to 2017 June 12) 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 confidenceAn untrusted search path vulnerability in the jizen_setup.exe installer allows attackers to achieve privilege escalation through DLL hijacking. The installer loads DLLs from directories that can be controlled by an attacker, who can place a malicious Trojan horse DLL to be loaded with elevated privileges during the installation process.
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<= -CVSS 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 jizen_setup.exe installer fileSearch filesystem for file named jizen_setup.exe using: find / -name jizen_setup.exe 2>/dev/null (Linux) or Get-ChildItem -Recurse -Filter jizen_setup.exe (Windows PowerShell)Affected if the file exists on the system and is the original unpatched installer
-
Check the file modification timestampInspect file properties to determine if the file was created or modified before June 12, 2017Affected if the file timestamp is prior to the June 12, 2017 patch release date
-
Identify the installation directoryLocate the directory where jizen_setup.exe is stored; examine if it is in a user-writable location such as a shared network folder, removable media, or a directory with weak permissionsAffected if the installer is stored in a directory writable by non-privileged users
-
Verify product installation presenceCheck for installed E Tax.nta E Tax product by querying installed programs or searching for related executables/directories: reg query HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall (Windows) or check common installation pathsAffected if the E Tax application is installed and the vulnerable installer remains on the system
-
Inspect DLL loading behaviorIf the installer is available, monitor its DLL loading by running process monitoring tools (procmon on Windows, strace/ltrace on Linux) during a test execution in an isolated environment, looking for DLL loads from user-controlled directoriesAffected if the installer loads DLLs from directories writable by standard users (indicating untrusted search path vulnerability)
A user is affected if the jizen_setup.exe installer file exists on their system and was not updated after the June 12, 2017 patch release, particularly if stored in a user-writable location.
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 dataUpdate to the patched version of jizen_setup.exe released after June 12, 2017, or remove the vulnerable installer from systems. Verify installer integrity via cryptographic checksums if using internal distribution.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2215 — 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-2215 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