CVE-2017-10848
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 Installers for DocuWorks 8.0.7 and earlier and DocuWorks Viewer Light published in Jul 2017 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 confidenceThe DocuWorks installer has an untrusted search path vulnerability where it loads DLLs from directories that can be controlled by an attacker. By placing a malicious DLL in an unspecified directory in the search path, an attacker can achieve code execution with the privileges of the user running the installer, potentially leading to 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<= 8.0.7<= 8.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.
-
Check DocuWorks installed versionOpen Windows Control Panel, go to Programs and Features, and locate 'Fujixerox DocuWorks' or 'Fujixerox DocuWorks Viewer Light' in the installed programs list. Note the version number shown in the Version column.Affected if The installed version is 8.0.7 or lower.
-
Check application directory for unknown DLLsNavigate to the DocuWorks installation directory (typically C:\Program Files\Fujixerox\DocuWorks or similar). Inspect all .dll files present. Look for DLLs that are not part of the standard installation or appear unexpected.Affected if Unexpected or unknown DLL files exist in the installation directory, particularly if they have recent modification dates or suspicious names.
-
Check user download or installer temp directoriesExamine directories where installer packages are commonly placed or extracted, such as the user's Downloads folder, Desktop, or temporary extraction folders. Look for any DLL files that were not intentionally placed there.Affected if Unsolicited DLL files are found in directories where DocuWorks installer packages are stored or extracted.
-
Review recent installer execution contextCheck Windows Event Viewer for recent installation events related to DocuWorks, particularly any failed or unusual DLL load events occurring during installation time.Affected if DLL load errors or warnings appear in event logs corresponding to DocuWorks installation attempts.
You are affected if DocuWorks or DocuWorks Viewer Light version 8.0.7 or lower is installed, and suspicious DLLs exist in installer-related directories.
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 DocuWorks to version 8.0.8 or later, and DocuWorks Viewer Light to the updated version published after July 2017. Ensure installers are run from secure directories and monitor for unauthorized DLL placement in installer directories.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10848 — 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-10848 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