# CVE-2017-12069: XML external entity in n/a

> An attacker can exploit an XML External Entity vulnerability in the OPC Discovery Server to access arbitrary resources via crafted packets.

- **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jj7f-wqmm-8q5f

## What is CVE-2017-12069?

CVE-2017-12069 is a high-severity vulnerability in n/a, published on 30 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An XXE vulnerability has been identified in OPC Foundation UA .NET Sample Code before 2017-03-21 and Local Discovery Server (LDS) before 1.03.367. Among the affected products are Siemens SIMATIC PCS7 (All versions V8.1 and earlier), SIMATIC WinCC (All versions < V7.4 SP1), SIMATIC WinCC Runtime Professional (All versions < V14 SP1), SIMATIC NET PC Software, and SIMATIC IT Production Suite. By sending specially crafted packets to the OPC Discovery Server at port 4840/tcp, an attacker might cause the system to access various resources chosen by the attacker.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

It affects 4 products.


Products: Ocpfoundation Local Discovery Server, Ocpfoundation Ua .Net, Siemens Simatic Pcs7, Siemens Wincc.

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

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

## Is CVE-2017-12069 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12069 is a high-severity vulnerability in n/a, published on 30 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12069 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-12069/ (Markdown: https://insights.sbomify.com/CVE-2017-12069/index.md)
```

## Sources

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

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