CVE-2017-3210
Last modified
CVE-2017-3210 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.91% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Portrait | Portrait Display Sdk | >= 2.30, < 2.34 |
| Fujitsu | Displayview Click | 6.0 |
| Fujitsu | Displayview Click | 6.01 |
| Fujitsu | Displayview Click Suite | 5.0 |
| Hp | Display Assistant | 2.1 |
| Hp | My Display | 2.0 |
| Philips | Smart Control Premium | 2.23 |
| Philips | Smart Control Premium | 2.25 |
References
- https://www.kb.cert.org/vuls/id/219739Third Party Advisory, US Government Resource
- https://www.securityfocus.com/bid/98006Third Party Advisory, VDB Entry
- https://www.kb.cert.org/vuls/id/219739Third Party Advisory, US Government Resource
- https://www.securityfocus.com/bid/98006Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-3210?
How severe is CVE-2017-3210?
How do I fix CVE-2017-3210?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-3203The Java implementations of AMF3 deserializers in Pivotal/Sp…
- CVE-2017-3204The Go SSH library (x/crypto/ssh) by default does not verify…8.1
- CVE-2017-3206The Java implementation of AMF3 deserializers used by Flamin…
- CVE-2017-3207The Java implementations of AMF3 deserializers in WebORB for…
- CVE-2017-3208The Java implementation of AMF3 deserializers used by WebORB…
- CVE-2017-3209The DBPOWER U818A WIFI quadcopter drone provides FTP access …8.1
- CVE-2017-3211Yopify, an e-commerce notification plugin, up to April 06, 2…5.3
- CVE-2017-3212The Space Coast Credit Union Mobile app 2.2 for iOS and 2.1.…5.9
- CVE-2017-3213The Think Mutual Bank Mobile Banking app 3.1.5 for iOS does …
- CVE-2017-3214The Milwaukee ONE-KEY Android mobile application stores the …7.5
- CVE-2017-3215The Milwaukee ONE-KEY Android mobile application uses bearer…
- CVE-2017-3216WiMAX routers based on the MediaTek SDK (libmtk) that use a …
Are you affected by CVE-2017-3210?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
