# CVE-2017-5176: Other in Rockwell Automation Connected Components Workbench

> DLL hijacking in Rockwell CCW allows attackers to execute arbitrary code and escalate privileges to administrator level on the victim's computer.

- **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:** 19 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cjwf-2ph9-3jpr

## What is CVE-2017-5176?

CVE-2017-5176 is a high-severity vulnerability in Rockwell Automation Connected Components Workbench, published on 19 May 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

A DLL Hijack issue was discovered in Rockwell Automation Connected Components Workbench (CCW). The following versions are affected: Connected Components Workbench - Developer Edition, v9.01.00 and earlier: 9328-CCWDEVENE, 9328-CCWDEVZHE, 9328-CCWDEVFRE, 9328-CCWDEVITE, 9328-CCWDEVDEE, 9328-CCWDEVESE, and 9328-CCWDEVPTE; and Connected Components Workbench - Free Standard Edition (All Supported Languages), v9.01.00 and earlier. Certain DLLs included with versions of CCW software can be potentially hijacked to allow an attacker to gain rights to a victim's affected personal computer. Such access rights can be at the same or potentially higher level of privileges as the compromised user account, including and up to computer administrator privileges.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Rockwellautomation Connected Components Workbench.

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

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

## Is CVE-2017-5176 being exploited?

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

## Other vulnerabilities in Rockwell Automation Connected Components Workbench

- [CVE-2021-27475](https://insights.sbomify.com/CVE-2021-27475/): Rockwell Automation Connected Components Workbench Deserialization of Untrusted Data (high 8.6)
- [CVE-2021-27471](https://insights.sbomify.com/CVE-2021-27471/): Rockwell Automation Connected Components Workbench Path Traversal (high 7.7)
- [CVE-2014-5424](https://insights.sbomify.com/CVE-2014-5424/): Code injection in n/a (high 7.5)
- [CVE-2021-27473](https://insights.sbomify.com/CVE-2021-27473/): Rockwell Automation Connected Components Workbench Improper Input Validation (medium 6.1)
- [CVE-2022-1018](https://insights.sbomify.com/CVE-2022-1018/): ICSA-22-088-01 Rockwell Automation ISaGRAF (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5176 is a high-severity vulnerability in Rockwell Automation Connected Components Workbench, published on 19 May 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-2017-5176 in the wild and no public exploit code.

Affected product: Rockwell Automation Connected Components Workbench. 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-5176/ (Markdown: https://insights.sbomify.com/CVE-2017-5176/index.md)
```

## Sources

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

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