dbcve.org
Portrait Display SdkApplication · Portrait

CVE-2017-3210

HIGH · 7.8 CVSS v3.0 Published 2018-07-24
Fix available
A fix is available. Upgrade to 2.34 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Applications developed using the Portrait Display SDK, versions 2.30 through 2.34, default to insecure configurations which allow arbitrary code execution. A number of applications developed using the Portrait Displays SDK do not use secure permissions when running. These applications run the component pdiservice.exe with NT AUTHORITY/SYSTEM permissions. This component is also read/writable by all Authenticated Users. This allows local authenticated attackers to run arbitrary code with SYSTEM privileges. The following applications have been identified by Portrait Displays as affected: Fujitsu DisplayView Click: Version 6.0 and 6.01. The issue was fixed in Version 6.3. Fujitsu DisplayView Click Suite: Version 5. The issue is addressed by patch in Version 5.9. HP Display Assistant: Version 2.1. The issue was fixed in Version 2.11. HP My Display: Version 2.0. The issue was fixed in Version 2.1. Philips Smart Control Premium: Versions 2.23, 2.25. The issue was fixed in Version 2.26.

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

The Portrait Display SDK (versions 2.30-2.34) creates a Windows service (pdiservice.exe) that runs with NT AUTHORITY/SYSTEM privileges but has insecure file permissions allowing all Authenticated Users to modify the executable. This enables local privilege escalation by replacing the service binary with malicious code that executes with SYSTEM-level privileges.

MitigationApply vendor-supplied updates: Fujitsu users to version 6.3/5.9, HP users to version 2.11/2.1, and Philips users to version 2.26. Alternatively, manually restrict pdiservice.exe permissions to administrators only until patches can be applied.

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
Portrait Display SdkApplication
Affected:>= 2.30, < 2.34
Displayview ClickApplication
Affected:= 6.0= 6.01
Displayview Click SuiteApplication
Affected:= 5.0
Display AssistantApplication
Affected:= 2.1
My DisplayApplication
Affected:= 2.0
Smart Control PremiumApplication
Affected:= 2.23= 2.25

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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. Locate pdiservice.exe
    Search for the file pdiservice.exe on the system. Common locations include C:\Program Files\Portrait Display\, C:\Program Files (x86)\Portrait Display\, or the installation directory of Fujitsu DisplayView, HP Display Assistant, HP My Display, or Philips Smart Control Premium.
    Affected if pdiservice.exe exists on the system and is from an affected version range (2.30-2.34 for Portrait SDK, or specific versions of Fujitsu/HP/Philips products)
  2. Determine installed product version
    Check the installed version of Portrait Display SDK, Fujitsu DisplayView Click/Suite, HP Display Assistant, HP My Display, or Philips Smart Control Premium via Windows Registry under HKLM\SOFTWARE\Portrait Display\ or the respective vendor's registry keys, or by checking the file properties of pdiservice.exe.
    Affected if The installed version is Portrait Display SDK >= 2.30 and < 2.34, Fujitsu Displayview Click 6.0 or 6.01, Fujitsu Displayview Click Suite 5.0, HP Display Assistant 2.1, HP My Display 2.0, or Philips Smart Control Premium 2.23 or 2.25
  3. Verify service exists
    Open Services console (services.msc) and look for a service named 'PDIService' or check via command: sc query pdiservice
    Affected if The PDIService Windows service is installed and running
  4. Check file permissions on pdiservice.exe
    Right-click pdiservice.exe in Windows Explorer, go to Security tab, or use icacls.exe: icacls "C:\path\to\pdiservice.exe" to view permissions. Verify if Authenticated Users or Users group has Write (W) or Modify (M) permissions.
    Affected if Authenticated Users or non-admin users have Write or Modify permissions to pdiservice.exe, allowing them to replace the executable

A user is affected if pdiservice.exe exists from an affected product version AND the service is installed AND non-administrative users have write permissions to the executable, enabling local privilege escalation to SYSTEM.

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
Upgrade available Upgrade to 2.34 or later
Fixed in 2.34
Interim mitigation

Apply vendor-supplied updates: Fujitsu users to version 6.3/5.9, HP users to version 2.11/2.1, and Philips users to version 2.26. Alternatively, manually restrict pdiservice.exe permissions to administrators only until patches can be applied.

Fix this in Portrait Display Sdk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3210 — 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-3210 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