# CVE-2017-3210: Privilege escalation in SDK

> Local attackers can escalate privileges to SYSTEM and execute arbitrary code due to insecure default permissions in applications using the Portrait Display SDK.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xc6c-wx39-jcrf

## What is CVE-2017-3210?

CVE-2017-3210 is a high-severity vulnerability in Portrait Display SDK, published on 24 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-16, CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2017-3210?

It affects 6 products.


Products: Fujitsu Displayview Click, Fujitsu Displayview Click Suite, Hp Display Assistant, Hp My Display, Philips Smart Control Premium, Portrait Portrait Display Sdk.

## How do I fix CVE-2017-3210?

No fix has been published for CVE-2017-3210 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-3210 being exploited?

There is no known exploitation of CVE-2017-3210 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3210 and fix it if it is affected.

What it is: CVE-2017-3210 is a high-severity vulnerability in Portrait Display SDK, published on 24 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3210 in the wild and no public exploit code.

Affected product: Portrait Display SDK. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-3210/ (Markdown: https://insights.sbomify.com/CVE-2017-3210/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-3210
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-3210
- OSV: https://osv.dev/vulnerability/CVE-2017-3210

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-3210/
Summaries are generated and may contain mistakes; the official description above is the record.