# CVE-2018-8076: Other in n/a

> A type confusion vulnerability in ZenMate for macOS allows attackers to cause a denial of service via malicious XPC messages.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 15 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cfq9-96fh-ph8f

## What is CVE-2018-8076?

CVE-2018-8076 is a high-severity vulnerability in n/a, published on 15 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ZenMate 1.5.4 for macOS suffers from a type confusion vulnerability within the com.zenmate.chron-xpc LaunchDaemon component. The LaunchDaemon implements an XPC service that uses an insecure XPC API for accessing data from an inbound XPC message. This could potentially result in an XPC object of the wrong type being passed as the first argument to the xpc_connection_create_from_endpoint function if controlled by an attacker. In recent versions of macOS and OS X, Apple has implemented an internal check to prevent such XPC API abuse from occurring, thus making this vulnerability only result in a denial of service if exploited by an attacker.

Weakness: CWE-704 (Incorrect Type Conversion or Cast)

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

It affects 1 product.


Products: Zenmate Zenmate.

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

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

## Is CVE-2018-8076 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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