CVE-2018-6669
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA whitelist bypass vulnerability in McAfee Application Control / Change Control 7.0.1 and before allows a remote or local user to execute blacklisted files through an ASP.NET form.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA whitelist bypass vulnerability in McAfee Application Control and Change Control 7.0.1 and earlier versions allows a remote or local authenticated user to execute blacklisted files through an ASP.NET form. The vulnerability indicates a flaw in the application's file execution controls where the blacklist mechanism can be circumvented via web form input handling.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 7.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify McAfee Application Control or Change Control is installedCheck for the presence of McAfee Application Control or Change Control software on the system - look for installed programs or services named 'McAfee Application Control' or 'McAfee Change Control' in Add/Remove Programs, program files, or Windows servicesAffected if The software is installed and the version cannot be determined or is 7.0.1 or earlier
-
Check the installed product versionLocate and read the version information for McAfee Application Control or Change Control - typically found in the product's UI under 'About' or in Windows registry under HKLM\SOFTWARE\McAfee\Application Control or similar paths, or via 'mcapictl --version' if the command-line tool existsAffected if The installed version is 7.0.1 or any version lower than 7.0.1 (e.g., 7.0.0, 6.x, 5.x)
-
Confirm ASP.NET integration is enabledCheck if ASP.NET is installed and configured on the system, and verify whether McAfee Application Control's web form handling feature is active - check IIS configuration for ASP.NET applications and any McAfee-related web modulesAffected if ASP.NET is installed and McAfee Application Control web form handling is active, allowing file uploads or submissions through web interfaces
-
Identify blacklist configuration and execution controlsReview McAfee Application Control or Change Control settings to identify the blacklist mechanism - check the product's console or configuration files for blacklisted file types, paths, or execution rulesAffected if A blacklist-based file execution control is configured and can be circumvented through web form input
You are affected if McAfee Application Control or Change Control version 7.0.1 or lower is installed with ASP.NET integration enabled and using a blacklist mechanism for file execution controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade McAfee Application Control / Change Control to a version beyond 7.0.1 that addresses this vulnerability, and implement additional input validation controls on ASP.NET forms to restrict file execution paths.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6669 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-6669 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data