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

> An unprotected XPC service in the Shimo VPN client helper allows local attackers to execute scripts as root, leading to privilege escalation.

- **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:** 7 Feb 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4gr9-9jg7-33hm

## What is CVE-2018-6823?

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

### Official description

In the VPN client in Mailbutler Shimo before 4.1.5.1 on macOS, the com.feingeist.shimo.helper tool LaunchDaemon implements an unprotected XPC service that can be abused to execute scripts as root.

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

It affects 1 product.


Products: Mailbutler Shimo.

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

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

## Is CVE-2018-6823 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-30328](https://insights.sbomify.com/CVE-2023-30328/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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