Mvision Endpoint Detection And ResponseApplication · Mcafee

CVE-2020-7327

MEDIUM · 6.7 CVSS v3.1 Published 2020-10-15
Fix available
A fix is available. Upgrade to 3.2.0 or later.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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 · unedited
Improperly implemented security check in McAfee MVISION Endpoint Detection and Response Client (MVEDR) prior to 3.2.0 may allow local administrators to execute malicious code via stopping a core Windows service leaving McAfee core trust component in an inconsistent state resulting in MVEDR failing open rather than closed

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 · high confidence

In McAfee MVISION EDR prior to version 3.2.0, the security check for protecting core components is improperly implemented. When a local administrator stops a core Windows service, the McAfee core trust component enters an inconsistent state, causing the MVEDR to fail open (disable protection) rather than fail closed (maintain protection). This allows malicious code execution.

MitigationUpgrade McAfee MVISION Endpoint Detection and Response Client to version 3.2.0 or later, which implements proper security checks that ensure the product fails closed when critical services are interrupted.

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
Mvision Endpoint Detection And ResponseApplication
Affected:< 3.2.0

CVSS 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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify MVISION EDR installation and version
    Check the installed version of McAfee MVISION Endpoint Detection and Response via Windows Registry at HKLM\SOFTWARE\McAfee\MVISION\EDR or by running 'Get-ItemProperty -Path "HKLM:\SOFTWARE\McAfee\MVISION\EDR" -Name Version' in PowerShell
    Affected if The installed version is lower than 3.2.0 or the product is not found (product not installed)
  2. Identify core MVISION EDR Windows services
    Open Services console (services.msc) and look for McAfee-related services with names containing 'MVISION', 'EDR', 'mvedr', or 'CoreShield' that are marked as core components
    Affected if Any of these core services are in a Stopped or Stopping state while the product is expected to be running
  3. Check protection status of the MVISION EDR client
    Open the MVISION EDR client console or run 'mvedrcli status' if available from command line, and verify whether real-time protection or threat prevention is reported as Enabled or Active
    Affected if Protection is reported as Disabled, Inactive, or Failed despite the product being installed
  4. Compare service state against expected behavior
    If a core McAfee service was recently stopped (check Event Viewer under Application logs for Service Control Manager events from McAfee), verify whether protection automatically re-enabled or remained disabled
    Affected if After stopping a core McAfee service, protection remains disabled rather than maintaining or resuming protection (fail-open behavior)

A user is affected if MVISION EDR version is below 3.2.0 AND core services are stopped, resulting in protection being disabled or failing to restore automatically.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 3.2.0 or later
Fixed in 3.2.0
Interim mitigation

Upgrade McAfee MVISION Endpoint Detection and Response Client to version 3.2.0 or later, which implements proper security checks that ensure the product fails closed when critical services are interrupted.

Fix this in Mvision Endpoint Detection And Response Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7327 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-7327 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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