dbcve.org
Virusscan EnterpriseApplication · Mcafee

CVE-2020-7337

MEDIUM · 6.7 CVSS v3.1 Published 2020-12-09
Fix available
A fix is available. Upgrade to 8.8 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
Incorrect Permission Assignment for Critical Resource vulnerability in McAfee VirusScan Enterprise (VSE) prior to 8.8 Patch 16 allows local administrators to bypass local security protection through VSE not correctly integrating with Windows Defender Application Control via careful manipulation of the Code Integrity checks.

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

McAfee VirusScan Enterprise prior to version 8.8 Patch 16 incorrectly integrates with Windows Defender Application Control, allowing local administrators to bypass Code Integrity protections through careful manipulation. This enables potential execution of unauthorized code despiteWDAC enforcement.

MitigationUpgrade McAfee VirusScan Enterprise to version 8.8 Patch 16 or later to ensure proper Windows Defender Application Control integration and Code Integrity 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
Virusscan EnterpriseApplication
Affected:< 8.8= 8.8

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. Identify VirusScan Enterprise version
    Open the McAfee VirusScan Enterprise console or check the program properties to find the installed version number and patch level
    Affected if version is less than 8.8 Patch 16 (including any 8.8 version without patch 16)
  2. Confirm Windows Defender Application Control is active
    Check Windows settings or use PowerShell to verify WDAC policies are enabled on the system
    Affected if WDAC policies are currently enforced on the system
  3. Verify Code Integrity enforcement status
    Inspect the Code Integrity event logs or system policy settings to confirm Code Integrity protections are active
    Affected if Code Integrity is being enforced through WDAC policies

A system is affected if it runs any version of McAfee VirusScan Enterprise prior to 8.8 Patch 16 while Windows Defender Application Control and Code Integrity enforcement are enabled.

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 8.8 or later
Fixed in 8.8
Interim mitigation

Upgrade McAfee VirusScan Enterprise to version 8.8 Patch 16 or later to ensure proper Windows Defender Application Control integration and Code Integrity enforcement.

Fix this in Virusscan Enterprise 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-7337 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-7337 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