CVE-2016-8354
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA vulnerability in Schneider Electric Unity PRO PLC Simulator allows arbitrary code execution through crafted x86 instructions in patched Unity project files. The simulator executes x86 instructions directly without proper validation, enabling an attacker to redirect control flow and execute malicious code by modifying the compiled Unity project.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 11.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Unity PRO versionLocate the installed Unity PRO application and check its version information through the application menu (Help > About) or the installer/program files metadata. Compare the version number to the affected range (11.0 and earlier).Affected if The installed version is 11.0 or lower.
-
Confirm PLC Simulator is in useVerify whether the Unity PRO installation includes the PLC Simulator component and whether it is actively used for testing or development. This can be confirmed by checking for simulator-specific project configurations or runtime settings within Unity PRO.Affected if The PLC Simulator component is installed and being used to load or simulate project files.
-
Inspect loaded Unity project filesReview the Unity project files (.apx, .xef, or related compiled project formats) currently loaded in the simulator. Check file properties and verify the source of these files, noting any recent modifications or imports from external or untrusted sources.Affected if Project files from untrusted or unknown sources have been loaded into the simulator, or files show signs of unexpected modification.
-
Check for unexpected execution behaviorMonitor the PLC Simulator for any unusual execution patterns, unexpected code execution, or anomalous behavior that could indicate control flow redirection. Review any logs or output generated during simulation.Affected if The simulator exhibits unexpected execution or behavior consistent with injected malicious code.
You are affected if Unity PRO version 11.0 or earlier is installed, the PLC Simulator is being used, and project files from untrusted sources have been loaded, creating conditions for arbitrary code execution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Unity PRO to V11.1 or later to remediate this vulnerability. Additionally, implement file integrity verification and only load Unity project files from trusted, validated sources.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-8354 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-8354 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data