# CVE-2016-9356: Privilege escalation in Moxa DACenter 1.4 and older

> An unquoted search path vulnerability in Moxa DACenter allows local attackers to execute arbitrary code with elevated privileges.

- **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:** 13 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fjg7-wjc5-q2pf

## What is CVE-2016-9356?

CVE-2016-9356 is a high-severity vulnerability in Moxa DACenter 1.4 and older, published on 13 Feb 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Moxa DACenter Versions 1.4 and older. The application may suffer from an unquoted search path issue.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Moxa Dacenter.

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

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

## Is CVE-2016-9356 being exploited?

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

## Other vulnerabilities in Moxa DACenter 1.4 and older

- [CVE-2016-9354](https://insights.sbomify.com/CVE-2016-9354/): Denial of service in Moxa DACenter 1.4 and older (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-9356 is a high-severity vulnerability in Moxa DACenter 1.4 and older, published on 13 Feb 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-9356 in the wild and no public exploit code.

Affected product: Moxa DACenter 1.4 and older. 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-9356/ (Markdown: https://insights.sbomify.com/CVE-2016-9356/index.md)
```

## Sources

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

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