CVE-2017-2226
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 Setup file of advance preparation for e-Tax software (WEB version) (1.17.1) 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 (untrusted search path) vulnerability in the setup file for e-Tax software WEB version 1.17.1 and earlier. The application loads DLLs without using safe search paths, allowing an attacker to place a malicious DLL in a directory that gets searched by the application, resulting in privilege escalation when the setup file runs.
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.17.1CVSS 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.1/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 e-Tax WEB versionLocate the e-Tax software installation and check the version information, typically found in the software's About or Properties window, or check the setup file version propertyAffected if The installed version is 1.17.1 or earlier
-
Locate the e-Tax setup fileFind the setup/installation executable file for e-Tax WEB version on the systemAffected if The setup file exists on the system and is version 1.17.1 or earlier
-
Inspect the setup file directory for unauthorized DLLsExamine the directory containing the e-Tax setup file for any unexpected or suspicious DLL files that are not part of the original packageAffected if There are unknown or untrusted DLL files in the same directory as the setup executable or in directories that the setup may search for DLLs (such as the application directory, current working directory, or system directories)
-
Check for writable directories in DLL search pathReview directories that the setup file might search for DLLs (including the setup directory itself, Windows system directories, and PATH directories) to determine if any are writable by untrusted usersAffected if Any directory in the DLL search path is writable by users other than the administrator, allowing them to place a malicious DLL
A user is affected if the e-Tax WEB version is 1.17.1 or earlier and the setup file or its search path directories contain untrusted DLLs that could be exploited 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 dataUpdate to the patched version of the e-Tax software (WEB version) when available. Avoid running the setup file from directories writable by other users, and ensure no untrusted DLLs are present in directories that the application may search.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2226 — 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-2226 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