dbcve.org
Apeosport ViApplication · Fujifilm

CVE-2017-10850

HIGH · 7.8 CVSS v3.1 Published 2017-09-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Untrusted search path vulnerability in Installers of ART EX Driver for ApeosPort-VI C7771/C6671/C5571/C4471/C3371/C2271, DocuCentre-VI C7771/C6671/C5571/C4471/C3371/C2271 (Timestamp of code signing is before 12 Apr 2017 02:04 UTC.), PostScript? Driver + Additional Feature Plug-in + PPD File for ApeosPort-VI C7771/C6671/C5571/C4471/C3371/C2271, DocuCentre-VI C7771/C6671/C5571/C4471/C3371/C2271 (Timestamp of code signing is before 12 Apr 2017 02:10 UTC.), XPS Print Driver for ApeosPort-VI C7771/C6671/C5571/C4471/C3371/C2271, DocuCentre-VI C7771/C6671/C5571/C4471/C3371/C2271 (Timestamp of code signing is before 3 Nov 2017 23:48 UTC.), ART EX Direct FAX Driver for ApeosPort-VI C7771/C6671/C5571/C4471/C3371/C2271, DocuCentre-VI C7771/C6671/C5571/C4471/C3371/C2271 (Timestamp of code signing is before 26 May 2017 07:44 UTC.), Setting Restore Tool for ApeosPort-VI C7771/C6671/C5571/C4471/C3371/C2271, DocuCentre-VI C7771/C6671/C5571/C4471/C3371/C2271 (Timestamp of code signing is before 25 Aug 2015 08:51 UTC.) 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 confidence

Untrusted search path (DLL hijacking) vulnerability in Xerox printer driver installers. Attackers can place a malicious DLL in an unspecified directory that gets loaded by the installer, executing with the privileges of the user running the installer. This affects multiple driver packages and tools for ApeosPort-VI and DocuCentre-VI printer models.

MitigationDeploy updated driver versions with code signing timestamps after the specified dates (April-November 2017), or ensure driver installation is performed from directories with restricted write permissions to prevent DLL planting.

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
Apeosport ViApplication
Affected:= c2271= c3371= c4471= c5571= c6671= c7771
Docucentre ViApplication
Affected:= c2271= c3371= c4471= c5571= c6671= c7771

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.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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed ApeosPort-VI or DocuCentre-VI printer drivers
    Open Windows Control Panel > Devices and Printers, or run 'Get-PrinterDriver' in PowerShell to list installed printer drivers. Look for driver names containing 'ApeosPort' or 'DocuCentre' along with model numbers c2271, c3371, c4471, c5571, c6671, or c7771.
    Affected if Any of these specific model numbers (c2271, c3371, c4471, c5571, c6671, c7771) appear in the installed printer driver name or driver package details.
  2. Check driver package version and installation date
    Right-click the printer in Devices and Printers > Printer Properties > Advanced tab, or use 'Get-PrinterDriver' PowerShell cmdlet to view driver version and date. Compare against the vulnerable timeframe (pre-April 2017 for most models, pre-November 2017 for some).
    Affected if Driver version is dated before April 2017 (or November 2017 for certain models) with no code signing timestamp after the mitigation dates.
  3. Verify driver source directory permissions
    Check the driver installation source location. If the driver was installed from a network share, USB drive, or directory with world-write permissions, right-click the directory > Properties > Security to verify who can write to it.
    Affected if The installation source directory allows write access to untrusted users, which could allow DLL planting.

Your environment is affected if you have installed ApeosPort-VI or DocuCentre-VI printer drivers with model numbers c2271, c3371, c4471, c5571, c6671, or c7771 dated before the April-November 2017 code signing timestamp updates.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Deploy updated driver versions with code signing timestamps after the specified dates (April-November 2017), or ensure driver installation is performed from directories with restricted write permissions to prevent DLL planting.

Fix this in Apeosport Vi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-10850 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-10850 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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