# CVE-2018-6700: True Key (TK) - DLL Search Order Hijacking vulnerability

> Local attackers can execute arbitrary code via DLL search order hijacking in McAfee True Key, requiring an upgrade to mitigate.

- **Severity:** High 7.5 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hh85-g72q-6wp5

## What is CVE-2018-6700?

CVE-2018-6700 is a high-severity vulnerability in McAfee True Key (TK), published on 24 Sep 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

DLL Search Order Hijacking vulnerability in Microsoft Windows Client in McAfee True Key (TK) before 5.1.165 allows local users to execute arbitrary code via specially crafted malware.

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 1 product.


Products: Mcafee True Key.

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

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

## Is CVE-2018-6700 being exploited?

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

## Other vulnerabilities in McAfee True Key (TK)

- [CVE-2018-6756](https://insights.sbomify.com/CVE-2018-6756/): True Key (TK) Windows Client - Authentication Abuse vulnerability (high 7.8)
- [CVE-2018-6757](https://insights.sbomify.com/CVE-2018-6757/): True Key (TK) Windows Client - Privilege Escalation vulnerability (high 7.5)
- [CVE-2018-6661](https://insights.sbomify.com/CVE-2018-6661/): TS102801 True Key DLL Side-Loading vulnerability (high 7.5)
- [CVE-2018-6755](https://insights.sbomify.com/CVE-2018-6755/): True Key (TK) Windows Client - Weak Directory Permission Vulnerability (high 7.2)
- [CVE-2018-6682](https://insights.sbomify.com/CVE-2018-6682/): True Key (TK) - Cross Site Scripting Exposure (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6700 is a high-severity vulnerability in McAfee True Key (TK), published on 24 Sep 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-6700 in the wild and no public exploit code.

Affected product: McAfee True Key (TK). 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-6700/ (Markdown: https://insights.sbomify.com/CVE-2018-6700/index.md)
```

## Sources

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

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