CVE-2020-7275
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 · uneditedAccessing, modifying or executing executable files vulnerability in the uninstaller in McAfee Endpoint Security (ENS) for Windows Prior to 10.7.0 April 2020 Update allows local users to execute arbitrary code via a carefully crafted input file.
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 confidenceA vulnerability in the McAfee Endpoint Security (ENS) for Windows uninstaller prior to version 10.7.0 allows local authenticated users to execute arbitrary code by providing a carefully crafted input file to the uninstaller process. This is a local privilege escalation issue stemming from improper handling of executable file paths during uninstallation.
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.5.0= 10.5.1= 10.5.2= 10.5.3= 10.5.4= 10.5.5= 10.6.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 Endpoint Security is installedCheck for the product in the Windows Registry under HKLM\SOFTWARE\McAfee\Endpoint Security\, or look for the installation directory under C:\Program Files\McAfee\Endpoint Security\Affected if The product is not found in registry or file system, meaning ENS is not installed
-
Identify the installed ENS versionQuery the Windows Registry value 'ProductVersion' under HKLM\SOFTWARE\McAfee\Endpoint Security\, or right-click the McAfee icon in the system tray and select 'About Endpoint Security'Affected if The displayed version matches any of: 10.5.0, 10.5.1, 10.5.2, 10.5.3, 10.5.4, 10.5.5, or 10.6.0
-
Confirm the uninstaller is presentLocate the uninstaller executable: look for 'McAfee Endpoint Security Uninstaller.exe' in the ENS installation directory (typically C:\Program Files\McAfee\Endpoint Security\), or check for the uninstallation entry in Add/Remove ProgramsAffected if The uninstaller executable exists on the system, which is required for the vulnerability to be exploitable
-
Check for recent uninstallation activityReview Windows Event Logs under Application and System event logs for events from 'MsiInstaller' or 'McAfee' related to uninstallation attempts, or check the uninstaller log files in the ENS directoryAffected if Uninstallation events or logs indicate the vulnerable uninstaller was recently executed
If McAfee Endpoint Security is installed with a version between 10.5.0 and 10.6.0 inclusive, the system is affected by this vulnerability when the uninstaller is present.
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 dataUpdate McAfee Endpoint Security for Windows to version 10.7.0 April 2020 Update or later. Apply the update through standard patch management processes after appropriate testing.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7275 — 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-2020-7275 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