# CVE-2018-13101: Privilege escalation in n/a

> Attackers can escalate privileges and execute arbitrary code by abusing exposed WCF methods in RedSwimmer KioskSimple that allow registry and service control.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-95q9-r6jm-cg3p

## What is CVE-2018-13101?

CVE-2018-13101 is a critical vulnerability in n/a, published on 3 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

KioskSimpleService.exe in RedSwimmer KioskSimple 1.4.7.0 suffers from a privilege escalation vulnerability in the WCF endpoint. The exposed methods allow read and write access to the Windows registry and control of services. These methods may be abused to achieve privilege escalation via execution of attacker controlled binaries.

## Which versions are affected by CVE-2018-13101?

It affects 1 product.


Products: Redswimmer Kiosksimple.

## How do I fix CVE-2018-13101?

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

## Is CVE-2018-13101 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-13101 and fix it if it is affected.

What it is: CVE-2018-13101 is a critical vulnerability in n/a, published on 3 Jul 2018. 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-2018-13101 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-2018-13101/ (Markdown: https://insights.sbomify.com/CVE-2018-13101/index.md)
```

## Sources

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

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