CVE-2019-3586
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 · uneditedProtection Mechanism Failure in the Firewall in McAfee Endpoint Security (ENS) 10.x prior to 10.6.1 May 2019 update allows context-dependent attackers to circumvent ENS protection where GTI flagged IP addresses are not blocked by the ENS Firewall via specially crafted malicious sites where the GTI reputation is carefully manipulated and does not correctly trigger the ENS Firewall to block the connection.
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 confidenceMcAfee Endpoint Security (ENS) 10.x Firewall fails to properly block GTI-flagged malicious IP addresses due to a flaw in how reputation data is processed. Attackers can circumvent ENS protection by crafting malicious sites that manipulate GTI reputation scoring, preventing the firewall from triggering block rules.
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.0.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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm McAfee Endpoint Security is installedCheck for ENS installation via registry key HKLM\SOFTWARE\McAfee\EndPointSecurity\CurrentVersion or look for McAfee Endpoint Security in installed programsAffected if McAfee Endpoint Security is present on the system
-
Check ENS version numberOpen the ENS interface and go to Help > About, or check the registry at HKLM\SOFTWARE\McAfee\EndPointSecurity\CurrentVersion for the Version valueAffected if Version is 10.0.0 through 10.6.1 (inclusive)
-
Verify Firewall module is enabledOpen ENS > Navigation > Firewall > Settings, or check registry under HKLM\SOFTWARE\McAfee\EndPointSecurity\Firewall\Policies for policy statusAffected if Firewall is enabled and active
-
Confirm GTI reputation feature is configuredOpen ENS > Navigation > Firewall > Settings > Reputation, or check if GTI is enabled in firewall policy settings. Look for Global Threat Intelligence or Reputation settings under firewall configurationAffected if GTI reputation scanning is enabled for the firewall policy in use
System is affected if ENS version is between 10.0.0 and 10.6.1, the Firewall module is enabled, and GTI reputation is being used for blocking decisions.
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 to McAfee Endpoint Security (ENS) 10.6.1 May 2019 update or later to remediate the vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3586 — 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-3586 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