CVE-2017-10851
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 for ContentsBridge Utility for Windows 7.4.0 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 · moderate confidenceThis is a DLL planting vulnerability where the ContentsBridge Utility installer for Windows loads DLLs from untrusted directories (untrusted search path). An attacker with write access to a directory in the DLL search path can place a malicious DLL that gets loaded by the installer, potentially executing code with the privileges of the user running the installer.
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<= 7.4.0CVSS 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 if ContentsBridge Utility is installedCheck for the presence of the Fujixerox ContentsBridge Utility in the system. Look in Program Files or Program Files (x86) for a folder named 'ContentsBridge' or similar Fujixerox utilities. On Windows, you can also check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry containing 'ContentsBridge'.Affected if ContentsBridge Utility is found installed on the system with version 7.4.0 or lower.
-
Determine the installed version of ContentsBridge UtilityRight-click the ContentsBridge executable or launcher, select Properties, then go to the Details tab to view the File Version. Alternatively, right-click the installer executable and check its version property.Affected if The version displayed is 7.4.0 or any version lower than 7.4.0.
-
Check the directory from which the installer or application is runExamine the location where ContentsBridge Utility is installed or the directory from which you launch it. Navigate to the installation folder and verify if it resides in a user-writable location such as Downloads, Temp, or a user home directory.Affected if The application or installer is run from or installed into a user-writable directory like Downloads, Temp folder, or any directory where untrusted users have write permissions.
-
Inspect the DLL search path behaviorUse a process monitoring tool like Process Monitor from Sysinternals to trace DLL loading when ContentsBridge Utility runs. Filter by the ContentsBridge process and observe which directories it attempts to load DLLs from, noting any that are user-writable.Affected if The process attempts to load DLLs from directories in the search path that are writable by other users, such as the application directory or system paths that allow user modification.
A user is affected if Fujixerox ContentsBridge Utility version 7.4.0 or lower is installed and is being run from or loads DLLs from a directory with write access for untrusted users.
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 relative DLL paths with absolute paths, enable safe DLL search mode (SetDllDirectory), or statically link required libraries. Users should ensure the installer runs from trusted directories and avoid running it from user-writable locations like downloads or temp folders.
- 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-10851 — 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-10851 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