Password ManagerApplication · Trendmicro

CVE-2022-28394

HIGH · 7.8 CVSS v3.1 Published 2022-05-27
Fix available
A fix is available. Upgrade to 3.7.0.1223 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
EOL Product CVE - Installer of Trend Micro Password Manager (Consumer) versions 3.7.0.1223 and below provided by Trend Micro Incorporated contains an issue with the DLL search path, which may lead to insecurely loading Dynamic Link Libraries (CWE-427). Please note that this was reported on an EOL version of the product, and users are advised to upgrade to the latest supported version (5.x).

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 confidence

The installer for Trend Micro Password Manager Consumer versions 3.7.0.1223 and below contains a DLL search path vulnerability (CWE-427 - Uncontrolled Search Path Element). This allows the application to potentially load malicious DLLs from untrusted locations instead of the intended secure locations, leading to code execution via DLL hijacking.

MitigationSince this is an End-of-Life product with no patch available, upgrade to the latest supported version (5.x). Users should also avoid running the installer from untrusted or shared directories to minimize DLL hijacking risk.

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
Password ManagerApplication
Affected:< 3.7.0.1223

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Find the installed version of Trend Micro Password Manager
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Trend Micro Password Manager*'} | Select-Object DisplayName, DisplayVersion
    Affected if The displayed version is 3.7.0.1223 or any version lower than 3.7.0.1223
  2. Check for all Trend Micro Password Manager installations
    Search using: Get-ChildItem -Path 'C:\Program Files', 'C:\Program Files (x86)' -Recurse -Directory -ErrorAction SilentlyContinue | Where-Object {$_.Name -like '*Trend Micro Password Manager*'}
    Affected if Any installation folder exists with version 3.7.0.1223 or below in the path or metadata
  3. Verify the specific vulnerable installer was used
    Check installer logs or system audit logs for occurrences of the MSI/EXE installer for version 3.7.0.1223 or lower, located in Windows\Installer folder or user's download history
    Affected if Evidence shows version 3.7.0.1223 or earlier of the installer was executed on this system

A system is affected if Trend Micro Password Manager Consumer version 3.7.0.1223 or any version below 3.7.0.1223 is currently installed or was installed using the vulnerable installer.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 3.7.0.1223 or later
Fixed in 3.7.0.1223
Interim mitigation

Since this is an End-of-Life product with no patch available, upgrade to the latest supported version (5.x). Users should also avoid running the installer from untrusted or shared directories to minimize DLL hijacking risk.

Recommended fix High confidence

5.x (latest supported version)

  1. 1. Back up any existing passwords or data from the current Trend Micro Password Manager installation (version 3.7.0.1223 or below)
  2. 2. Uninstall the current version of Trend Micro Password Manager from the system
  3. 3. Download the latest supported version (5.x) of Trend Micro Password Manager from the official Trend Micro website
  4. 4. Install the downloaded version 5.x following the on-screen instructions
  5. 5. Restore or re-import the backed-up password data into the new version
Caveat May require migration of password data; ensure backup before uninstalling old version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Password Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28394 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-28394 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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