CVE-2019-3637
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 McAfee FRP 5.x prior to 5.1.0.209 allows local users to gain elevated privileges via running McAfee Tray with elevated privileges.
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 a local privilege escalation vulnerability in McAfee FRP (File Request Proxy) 5.x versions prior to 5.1.0.209. The McAfee Tray component can be run with elevated privileges, allowing a local unprivileged user to gain elevated access to the system.
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>= 5.0.0, < 5.1.0.209CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 FRP version installedOpen Windows Control Panel, navigate to Programs and Features, or use 'wmic product get name,version' to list installed McAfee products. Look for 'McAfee File and Removable Media Protection' or 'McAfee FRP' and note the version number.Affected if The installed version is 5.0.0 or higher but lower than 5.1.0.209
-
Locate McAfee Tray componentOpen Task Manager and look for a process named 'McTray.exe' or 'mcapexe.exe' running under the current user session. Also check for McAfee-related services in Services.msc.Affected if The McAfee Tray component (McTray.exe) is present and running on the system
-
Verify elevated privilege contextIn Task Manager, right-click the McTray.exe process and select 'Run as administrator' to confirm if it can be executed with elevated privileges. Check the service configuration for any FRP-related services in Services.msc to see if they run under SYSTEM or an administrator account.Affected if The McAfee Tray component can be run with elevated (administrator or SYSTEM) privileges, allowing a local unprivileged user to potentially escalate privileges
A system is affected if McAfee File and Removable Media Protection version is 5.0.0 or higher but below 5.1.0.209 and the McAfee Tray component is present and can be executed with elevated privileges.
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 data5.1.0.209
Upgrade McAfee FRP to version 5.1.0.209 or later to obtain the patched component that properly handles privilege escalation.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3637 — 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-3637 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