Vulnerability Note VU#219739
Portrait Displays SDK applications are vulnerable to arbitrary code execution and privilege escalation
Original Release date: 25 Apr 2017 | Last revised: 25 Apr 2017
Applications developed using the Portrait Display SDK, versions 2.30 through 2.34, default to insecure configurations which allow arbitrary code execution.
CWE-276: Incorrect Default Permissions – CVE-2017-3210
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
A local authenticated (non-privileged) attacker can run arbitrary code with SYSTEM privileges.
Apply an update
Ensure that affected applications are updated to the most recent versions.
Portrait Displays has provided patch for affected applications.
If you are unable to update your software, please see the following workarounds:
Manually remove unsafe permissions
Using the following command you can remove read/write permissions from "Authenticated Users":
sc sdset pdiservice D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)
Vendor Information (Learn More)
VendorStatusDate NotifiedDate UpdatedPortrait DisplaysAffected15 Mar 201724 Apr 2017If you are a vendor and your product is affected, let
CVSS Metrics (Learn More)
Thanks to Werner Schober of SEC Consult for reporting this vulnerability.
This document was written by Trent Novelly.
24 Apr 2017
Date First Published:
25 Apr 2017
Date Last Updated:
25 Apr 2017
FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.