CVE-2018-6664
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 · uneditedApplication Protections Bypass vulnerability in Microsoft Windows in McAfee Data Loss Prevention (DLP) Endpoint before 10.0.500 and DLP Endpoint before 11.0.400 allows authenticated users to bypass the product block action via a command-line utility.
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 confidenceMcAfee DLP Endpoint contains an application protection bypass vulnerability that allows authenticated Windows users to circumvent the product's block actions using a specific command-line utility. This enables users to potentially bypass data loss prevention controls and exfiltrate data despite the DLP policy enforcement.
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< 10.0.500< 11.0.400CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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 DLP Endpoint is installedCheck Windows installed programs list, or look for the 'McAfee DLP Endpoint' service in Services.msc, or query the registry at HKLM\SOFTWARE\McAfee\DLP for the product entry.Affected if The product is not found on the system.
-
Determine installed DLP Endpoint versionQuery the Windows registry key HKLM\SOFTWARE\McAfee\DLP\CurrentVersion for the 'Version' value, or use the McAfee ePO console to check the installed product version if centrally managed.Affected if The retrieved version is lower than 10.0.500 for the 10.x branch or lower than 11.0.400 for the 11.x branch.
-
Check for vulnerable command-line utility presenceLocate the specific CLI utility referenced in the CVE documentation that can be used to bypass DLP controls; this is typically found in the DLP installation directory under the bin or tools subfolder.Affected if The CLI utility exists on the system and can be executed by an authenticated user.
-
Confirm DLP block policies are configuredReview the DLP policy settings in the McAfee ePO console or local DLP policy configuration to verify if block actions are enabled for any data protection rules.Affected if Block actions are actively enforced and the version is vulnerable.
A user is affected if McAfee DLP Endpoint is installed with a version below 10.0.500 (10.x branch) or below 11.0.400 (11.x branch), and block policies are configured.
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 data10.0.50011.0.400
Upgrade McAfee DLP Endpoint to version 10.0.500 or later (for 10.x branch) or version 11.0.400 or later (for 11.x branch) to remediate this bypass vulnerability.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6664 — 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-6664 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