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

> A local attacker can escalate privileges to SYSTEM by exploiting the TunnelBearMaintenance service to load a malicious OpenVPN plugin.

- **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:** 26 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mh68-r8rp-2j3j

## What is CVE-2018-10381?

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

### Official description

TunnelBear 3.2.0.6 for Windows suffers from a SYSTEM privilege escalation vulnerability through the "TunnelBearMaintenance" service. This service establishes a NetNamedPipe endpoint that allows arbitrary installed applications to connect and call publicly exposed methods. The "OpenVPNConnect" method accepts a server list argument that provides attacker control of the OpenVPN command line. An attacker can specify a dynamic library plugin that should run for every new VPN connection attempt. This plugin will execute code in the context of the SYSTEM user.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Mcafee Tunnelbear.

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

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

## Is CVE-2018-10381 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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