CVE-2019-14687
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 · uneditedA DLL hijacking vulnerability exists in Trend Micro Password Manager 5.0 in which, if exploited, would allow an attacker to load an arbitrary unsigned DLL into the signed service's process. This process is very similar, yet not identical to CVE-2019-14684.
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 confidenceTrend Micro Password Manager 5.0 is vulnerable to DLL hijacking, allowing an attacker to place a malicious unsigned DLL in a location from which the application loads DLLs. When the signed service process loads this arbitrary DLL, it executes with the trusted status of the signed process, enabling privilege escalation and code execution.
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.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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.
-
Verify Trend Micro Password Manager 5.0 is installedCheck for the product in installed programs (Control Panel > Programs and Features) or look for the installation directory typically under C:\Program Files\Trend Micro\Password Manager or C:\Program Files (x86)\Trend Micro\Password ManagerAffected if The product shows as Trend Micro Password Manager version 5.0
-
Identify the Password Manager service executableLook for the service process (commonly PasswordManagerService.exe or similar) in the installation directory or running services using Task Manager or sc query commandAffected if The service process tmPMSvc.exe or PasswordManagerService.exe exists and is running
-
Check DLL search path permissionsExamine write permissions on directories in the application DLL search path, particularly the current working directory, installation folder, and system paths. Use icacls or accesschk to enumerate writable locations.Affected if Any untrusted user has write access to directories from which the application loads DLLs (especially the application directory or current working directory)
-
Verify if unsigned DLLs can be loadedReview the application configuration and monitoring for DLL loading behavior. Check if the application loads DLLs without signature validation by inspecting the application logs or using process monitoring tools.Affected if The application loads DLLs from user-writable locations without requiring valid signatures
You are affected if Trend Micro Password Manager version 5.0 is installed AND an untrusted user can write to any DLL search path used by the service process.
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 dataApply vendor-supplied patches for Trend Micro Password Manager 5.0. As a temporary workaround, ensure no untrusted DLLs can be placed in directories searched by the application (e.g., current working directory, system paths).
- Consultation2.0 h
- Implementation6.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14687 — 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-14687 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