# CVE-2016-8354: Code injection in Schneider Electric Unity PRO Control prior to V11.1

> Attackers can execute arbitrary code by crafting a malicious Unity project file that exploits the PLC Simulator's direct execution of x86 instructions.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m337-hwf6-792v

## What is CVE-2016-8354?

CVE-2016-8354 is a high-severity code injection vulnerability in Schneider Electric Unity PRO Control prior to V11.1, published on 13 Feb 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in Schneider Electric Unity PRO prior to V11.1. Unity projects can be compiled as x86 instructions and loaded onto the PLC Simulator delivered with Unity PRO. These x86 instructions are subsequently executed directly by the simulator. A specially crafted patched Unity project file can make the simulator execute malicious code by redirecting the control flow of these instructions.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Schneider-Electric Unity Pro.

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

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

## Is CVE-2016-8354 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8354 is a high-severity code injection vulnerability in Schneider Electric Unity PRO Control prior to V11.1, published on 13 Feb 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-8354 in the wild and no public exploit code.

Affected product: Schneider Electric Unity PRO Control prior to V11.1. 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-8354/ (Markdown: https://insights.sbomify.com/CVE-2016-8354/index.md)
```

## Sources

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

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