CVE-2017-2189
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 RW-4040 driver installer for Windows 7 version 2.27 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 in the Canon RW-4040 driver installer version 2.27 for Windows 7. The installer searches for DLLs in untrusted paths, allowing an attacker to place a malicious DLL that gets loaded during installation, resulting in privilege escalation.
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= 2.27CVSS 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.
-
Identify installed Canon RW-4040 driver versionCheck Programs and Features in Control Panel, or examine the driver installation directory for version information. Look for 'RW-4040' or 'Canon RW-4040' in installed programs.Affected if The installed driver version is exactly 2.27
-
Locate the Canon RW-4040 installer executableSearch for files named 'RW-4040' or 'Canon' installer files (.exe or .msi) in typical download directories, temp folders, or installation media. Check the file properties for version information.Affected if An installer file with version 2.27 exists on the system
-
Verify Windows versionRun 'winver' or check System Properties. This vulnerability specifically affects Windows 7.Affected if The system is running Windows 7 and has the affected driver version installed
-
Check for suspicious DLLs in installer search pathsExamine directories where the installer may have been run from (downloads folder, removable media, network shares) for unexpected DLL files that may have been loaded. Look for DLLs with timestamps matching or shortly after the installer execution time.Affected if Unexpected DLL files exist in directories where the installer was executed from
-
Review installation logs for DLL load eventsCheck Windows Installer logs (in %TEMP% or %WINDIR%\Logs) or any Canon installation logs for evidence of DLL loading from non-system paths.Affected if Logs indicate DLLs were loaded from user-writable directories such as the installer directory or temp folders
The system is affected if the Canon RW-4040 driver version 2.27 is installed on Windows 7 and the installer was executed from a directory where an attacker could place a malicious DLL.
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 dataDo not run the RW-4040 driver installer version 2.27 in untrusted or multi-user environments. Wait for an official vendor patch from Canon that properly secures the DLL search path, and verify the integrity of any installer before execution.
- Consultation2.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2189 — 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-2189 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