# CVE-2016-8561: Privilege escalation in n/a

> Users with elevated TIA-Portal privileges can gain privileged access on affected SIMATIC CP devices, requiring an upgrade to mitigate.

- **Severity:** Medium 6.6 (`CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6xmx-v4m3-j532

## What is CVE-2016-8561?

CVE-2016-8561 is a medium-severity vulnerability in n/a, published on 18 Nov 2016. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability has been identified in SIMATIC CP 1543-1 (All versions < V2.0.28), SIPLUS NET CP 1543-1 (All versions < V2.0.28). Users with elevated privileges to TIA-Portal and project data on the engineering station could possibly get privileged access on affected devices.

Weakness: CWE-264

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

It affects 1 product.


Products: Siemens Simatic Cp 1543-1 Firmware.

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

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

## Is CVE-2016-8561 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-8562](https://insights.sbomify.com/CVE-2016-8562/): Siemens SIMATIC CP 1543-1 Improper Privilege Management (high 7.5, exploited in the wild)
- [CVE-2024-50310](https://insights.sbomify.com/CVE-2024-50310/): Missing authorization in SIMATIC CP 1543-1 V4.0 (high 8.7)
- [CVE-2021-33716](https://insights.sbomify.com/CVE-2021-33716/): Information disclosure in SIMATIC CP 1543-1 (incl. SIPLUS variants) (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8561 is a medium-severity vulnerability in n/a, published on 18 Nov 2016. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-8561 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-2016-8561/ (Markdown: https://insights.sbomify.com/CVE-2016-8561/index.md)
```

## Sources

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

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