# CVE-2018-6668: Bypass Application Control with simple DLL

> Attackers can bypass application whitelisting controls to execute arbitrary code via DLLs and interpreters like PowerShell.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Dec 2018
- **Updated:** 6 May 2025
- **Also known as:** GHSA-hqj3-m7hv-fj29

## What is CVE-2018-6668?

CVE-2018-6668 is a medium-severity vulnerability in McAfee Application and Change Control, published on 31 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A whitelist bypass vulnerability in McAfee Application Control / Change Control 7.0.1 and before allows execution bypass, for example, with simple DLL through interpreters such as PowerShell.

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

It affects 1 product.


Products: Mcafee Application Change Control.

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

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

## Is CVE-2018-6668 being exploited?

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

## Other vulnerabilities in McAfee Application and Change Control

- [CVE-2018-6669](https://insights.sbomify.com/CVE-2018-6669/): Bypass Application Control through an ASP.NET form (medium 6.3)
- [CVE-2018-6690](https://insights.sbomify.com/CVE-2018-6690/): McAfee Application Control (MAC) - Whitelist bypass using a hard drive solidified by MACC (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6668 is a medium-severity vulnerability in McAfee Application and Change Control, published on 31 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-6668 in the wild and no public exploit code.

Affected product: McAfee Application and Change Control. 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-6668/ (Markdown: https://insights.sbomify.com/CVE-2018-6668/index.md)
```

## Sources

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

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