# CVE-2016-10323: Privilege escalation in n/a

> Local attackers can escalate privileges by exploiting setuid execution in Synology Photo Station, requiring an upgrade to mitigate.

- **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:** 10 Apr 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5pcc-783h-f9f4

## What is CVE-2016-10323?

CVE-2016-10323 is a high-severity vulnerability in n/a, published on 10 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Synology Photo Station before 6.3-2958 allows local users to gain privileges by leveraging setuid execution of a "synophoto_dsm_user --copy-no-ea" command.

Weakness: CWE-264

## Which versions are affected by CVE-2016-10323?

It affects 1 product.


Products: Synology Photo Station.

## How do I fix CVE-2016-10323?

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

## Is CVE-2016-10323 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-29089](https://insights.sbomify.com/CVE-2021-29089/): SQL injection in Synology Photo Station (critical 9.8)
- [CVE-2017-11161](https://insights.sbomify.com/CVE-2017-11161/): SQL injection in Synology Photo Station (critical 9.8)
- [CVE-2017-11151](https://insights.sbomify.com/CVE-2017-11151/): File upload in Synology Photo Station (critical 9.8)
- [CVE-2017-11153](https://insights.sbomify.com/CVE-2017-11153/): Deserialization in Synology Photo Station (critical 9.8)
- [CVE-2016-10329](https://insights.sbomify.com/CVE-2016-10329/): Command injection in Synology Photo Station (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10323 and fix it if it is affected.

What it is: CVE-2016-10323 is a high-severity vulnerability in n/a, published on 10 Apr 2017. 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-2016-10323 in the wild and no public exploit code.

Affected product: n/a. 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-2016-10323/ (Markdown: https://insights.sbomify.com/CVE-2016-10323/index.md)
```

## Sources

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

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