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

> Non-admin users can execute telegram simulation via cached data if an admin previously ran it and closed the connection, requiring local access and specific preconditions.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h78p-6x92-8qgr

## What is CVE-2016-10041?

CVE-2016-10041 is a high-severity vulnerability in n/a, published on 25 Dec 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Sprecher Automation SPRECON-E Service Program before 3.43 SP0. Under certain preconditions, it is possible to execute telegram simulation as a non-admin user. As prerequisites, a user must have created an online-connection, validly authenticated and authorized as administrator, and executed telegram simulation. After that, the online-connection must have been closed. Incorrect caching of client data then may lead to privilege escalation, where a subsequently acting non-admin user is permitted to do telegram simulation. In order to exploit this vulnerability, a potential attacker would need to have both a valid engineering-account in the SPRECON RBAC system as well as access to a service/maintenance computer with SPRECON-E Service Program running. Additionally, a valid admin-user must have closed the service connection beforehand without closing the program, having executed telegram simulation; the attacker then has access to the running software instance. Hence, there is no risk from external attackers.

Weakness: CWE-264

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

It affects 1 product.


Products: Sprecher-Automation Sprecon-E Service Program.

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

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

## Is CVE-2016-10041 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-10041 is a high-severity vulnerability in n/a, published on 25 Dec 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-10041 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-10041/ (Markdown: https://insights.sbomify.com/CVE-2016-10041/index.md)
```

## Sources

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

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