CVE-2019-3652
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 · uneditedCode Injection vulnerability in EPSetup.exe in McAfee Endpoint Security (ENS) Prior to 10.6.1 October 2019 Update allows local user to get their malicious code installed by the ENS installer via code injection into EPSetup.exe by an attacker with access to the installer.
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 local attacker with access to the McAfee Endpoint Security installer (EPSetup.exe) can inject malicious code that gets executed during the installation process, allowing arbitrary code execution with the privileges of the installer. The vulnerability exists in ENS versions prior to 10.6.1 October 2019 Update.
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.5>= 10.6.0, < 10.6.1= 10.6.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
- 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 presence of McAfee Endpoint Security on the system. This can be done via Windows Programs and Features, or by checking for the installation directory (commonly at C:\Program Files\McAfee\Endpoint Security).Affected if McAfee Endpoint Security is not installed on the system
-
Determine the installed Endpoint Security versionOpen Windows Programs and Features, find McAfee Endpoint Security, and note the version column. Alternatively, open the ENS installation directory and check the version info of the main executable.Affected if The installed version is 10.5.0 through 10.5.5, 10.6.0 through 10.6.1 (any build before the October 2019 Update), or exactly 10.6.1
-
Locate EPSetup.exe installer filesSearch the system for EPSetup.exe or any McAfee installer files. Check common download locations, temp folders, and network shares where installers may be stored.Affected if EPSetup.exe or other ENS installer files are found on the system, especially in non-standard or shared locations
-
Verify installer source integrityReview how the installer was obtained. Check if it was downloaded from official McAfee sources, downloaded from third-party sites, or obtained from internal network shares without checksum validation.Affected if The installer was obtained from unofficial sources, third-party websites, or shared network locations without cryptographic verification
A system is affected if McAfee Endpoint Security version falls within 10.5.0 to 10.5.5, 10.6.0 to 10.6.1, or exactly 10.6.1, and the installer (EPSetup.exe) was obtained from or stored in non-official locations where tampering could have occurred.
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.6.1
Upgrade to McAfee Endpoint Security 10.6.1 October 2019 Update or later. Additionally, verify installer integrity by obtaining from official McAfee sources and validating checksums before execution.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3652 — 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-2019-3652 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