CVE-2019-3610
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 · uneditedData Leakage Attacks vulnerability in Microsoft Windows client in McAfee True Key (TK) 3.1.9211.0 and earlier allows local users to expose confidential data via specially crafted malware.
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 confidenceLocal privilege escalation vulnerability in McAfee True Key 3.1.9211.0 and earlier allows specially crafted malware to access confidential data stored by the password manager, likely due to improper access controls on sensitive storage.
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<= 3.1.9211.0CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 if McAfee True Key is installedCheck for the presence of McAfee True Key in the system - look for the application in installed programs (Windows: Control Panel > Programs and Features, or check C:\Program Files\McAfee\True Key or C:\Program Files (x86)\McAfee\True Key directories)Affected if McAfee True Key is present on the system
-
Determine the installed version of McAfee True KeyCheck the version of the installed True Key application - in Windows, right-click the executable properties, or look in the Windows Registry under HKLM\SOFTWARE\McAfee\True Key or HKLM\SOFTWARE\WOW6432Node\McAfee\True Key for the Version valueAffected if The installed version is 3.1.9211.0 or any earlier version
-
Locate True Key user data directoriesIdentify where True Key stores sensitive data - typically found in the user's AppData folder (e.g., %APPDATA%\McAfee\True Key or %LOCALAPPDATA%\McAfee\True Key)Affected if True Key user data directories exist and the application is installed in a vulnerable version
-
Verify access permissions on sensitive storage locationsExamine file system permissions on the True Key data directories - use icacls or check security properties to see if low-privilege users or processes can access these foldersAffected if Non-admin users or processes have excessive read/write access to True Key confidential data folders
-
Monitor for suspicious process activity targeting True Key dataReview process creation logs or endpoint detection for processes attempting to access True Key storage directories, especially from unexpected or malicious sourcesAffected if Suspicious processes are observed accessing True Key user data directories
A system is affected if McAfee True Key version 3.1.9211.0 or earlier is installed and the sensitive data storage locations have overly permissive access controls that allow unauthorized access.
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 dataUpdate McAfee True Key to a version newer than 3.1.9211.0 to patch the vulnerability; ensure endpoint protection monitors for suspicious processes targeting True Key user data directories.
- 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-3610 — 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-3610 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