CVE-2019-3582
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 · uneditedPrivilege Escalation vulnerability in Microsoft Windows client in McAfee Endpoint Security (ENS) 10.6.1 and earlier allows local users to gain elevated privileges via a specific set of circumstances.
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 Endpoint Security (ENS) 10.6.1 and earlier on Windows clients contains a local privilege escalation vulnerability that allows an unprivileged local user to gain elevated privileges through a specific set of circumstances. This is a vulnerability in a security product itself, which is particularly concerning as it could allow an attacker to bypass the endpoint protection.
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.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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/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.
-
Identify installed McAfee Endpoint Security versionOpen Windows Control Panel > Programs and Features, or run 'wmic product get name,version' and look for 'McAfee Endpoint Security' or 'McAfee Endpoint Protection' in the listAffected if The installed version is 10.6.1 or any version lower than 10.6.1
-
Check ENS version via Windows RegistryOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\McAfee\Endpoint Security or check the version value in the McAfee product installation directory typically under C:\Program Files\McAfee\Endpoint SecurityAffected if The version value returned is 10.6.1 or lower
-
Verify product is ENS for Windows ClientsConfirm the installed product is specifically McAfee Endpoint Security (ENS) for Windows clients, not server versions or other McAfee products - check the product name in Programs and Features or the installation directory nameAffected if The product is ENS 10.6.1 or earlier on a Windows client operating system
A user is affected if McAfee Endpoint Security version 10.6.1 or earlier is installed on a Windows client system, as this version contains the local privilege escalation vulnerability.
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 dataUpgrade McAfee Endpoint Security to a version newer than 10.6.1 that includes the security fix. Prioritize patching on systems with local non-privileged users who may have access to the same machine.
- Consultation3.0 h
- Implementation2.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 $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3582 — 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-3582 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