# CVE-2017-12070: Supply chain in n/a

> Attackers can replace unsigned OPC Foundation DLLs with malicious code to execute arbitrary commands on affected systems.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c2m3-cg53-fc7m

## What is CVE-2017-12070?

CVE-2017-12070 is a high-severity vulnerability in n/a, published on 14 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Unsigned versions of the DLLs distributed by the OPC Foundation may be replaced with malicious code.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Opcfoundation Ua-.Net-Legacy.

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

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

## Is CVE-2017-12070 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-12585](https://insights.sbomify.com/CVE-2018-12585/): XML external entity in n/a (high 8.2)
- [CVE-2021-27432](https://insights.sbomify.com/CVE-2021-27432/): Denial of service in OPC Foundation OPC UA .NET Standard and OPC UA .NET Legacy (high 7.5)
- [CVE-2018-12087](https://insights.sbomify.com/CVE-2018-12087/): Moderate severity vulnerability that affects OPCFoundation.NetStandard.Opc.Ua (medium 5.3)
- [CVE-2018-7559](https://insights.sbomify.com/CVE-2018-7559/): OPC UA applications can allow a remote attacker to determine a Server's private key (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12070 is a high-severity vulnerability in n/a, published on 14 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-12070 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-2017-12070/ (Markdown: https://insights.sbomify.com/CVE-2017-12070/index.md)
```

## Sources

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

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