CVE-2019-3584
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 · uneditedExploitation of Authentication vulnerability in MVision Endpoint in McAfee MVision Endpoint Prior to 1811 Update 1 (18.11.31.62) allows authenticated administrator users --> administrators to Remove MVision Endpoint via unspecified vectors.
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 confidenceThis is an authentication vulnerability in McAfee MVision Endpoint that allows an authenticated administrator user to remove/uninstall the MVision Endpoint security product via unspecified vectors. The vulnerability exists in versions prior to 1811 Update 1 (18.11.31.62).
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< 18.11.31.62CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:N/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.
-
Confirm MVision Endpoint is installedCheck for MVision Endpoint installation: On Windows, look in Program Files for 'McAfee MVision Endpoint' or check Add/Remove Programs. On Linux, run 'rpm -qa | grep -i mvision' or 'dpkg -l | grep -i mvision'. On macOS, check /Applications for MVision app or run 'ls /Applications | grep -i mvision'.Affected if MVision Endpoint is not present on the system, then the CVE does not apply
-
Determine installed version numberOn Windows: Open Control Panel > Programs and Features > select McAfee MVision Endpoint > note the version in the 'Version' column. Or run: 'wmic product get name,version' and filter for MVision. On Linux: Run 'rpm -qa | grep -i mvision' or check /opt/McAfee/mvision/VERSION file if it exists. On macOS: Right-click MVision app in Applications > Get Info > note the Version field.Affected if Version cannot be determined or the product is installed but version field is empty/missing
-
Compare version to affected rangeCompare the installed version number to 18.11.31.62. Version strings should be compared numerically: if the installed version is 18.11.x.x where x is any number less than 31.62, or any version earlier than 18.11 (such as 18.7, 18.0, etc.), it is in the affected range. Versions 18.11.31.62 and later are NOT affected.Affected if Installed version is less than 18.11.31.62 (for example: 18.11.31.0, 18.11.0.0, 18.7.0.0, or any 18.x.x.x version below 18.11.31.62)
The environment is affected only if McAfee MVision Endpoint is installed AND the installed version is lower than 18.11.31.62.
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 data18.11.31.62
Upgrade McAfee MVision Endpoint to version 18.11.31.62 or later. Apply the vendor-supplied patch following standard change management procedures.
- Consultation4.0 h
- Implementation3.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3584 — 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-3584 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