dbcve.org
Password ManagerApplication · Trendmicro

CVE-2022-30523

HIGH · 7.8 CVSS v3.1 Published 2022-05-16
Fix available
A fix is available. Upgrade to 5.0.0.1270 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Trend Micro Password Manager (Consumer) version 5.0.0.1266 and below is vulnerable to a Link Following Privilege Escalation Vulnerability that could allow a low privileged local attacker to delete the contents of an arbitrary folder as SYSTEM which can then be used for privilege escalation on the affected machine.

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 confidence

A link following vulnerability in Trend Micro Password Manager allows a low-privileged local attacker to manipulate symbolic links or junctions to delete arbitrary folder contents with SYSTEM-level privileges, enabling local privilege escalation.

MitigationUpdate Trend Micro Password Manager to a version newer than 5.0.0.1266. As a compensating control, restrict file system permissions on directories accessible by the application to prevent low-privileged users from creating symlinks or junctions in those locations.

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:< 5.0.0.1270

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Identify installed Trend Micro Password Manager version
    Check the application version through Windows Programs and Features, the application's About dialog, or the program's executable file properties. Common install paths include C:\Program Files\Trend Micro\Password Manager or C:\Program Files (x86)\Trend Micro\Password Manager. Right-click the main .exe file and view Details to see the Product Version.
    Affected if The installed version is lower than 5.0.0.1270
  2. Verify Trend Micro Password Manager is running
    Open Task Manager or run 'tasklist /FI "IMAGENAME eq PasswordManager.exe"' from command prompt to check if the Trend Micro Password Manager process is currently active.
    Affected if The application process is running while a low-privileged user has write access to directories the application uses
  3. Check user permissions on application data directories
    Run 'icacls "C:\ProgramData\Trend Micro"' and 'icacls "%LOCALAPPDATA%\Trend Micro"' (adjust paths if installed elsewhere) to list which users have write permissions to directories where the application stores data.
    Affected if Low-privileged standard users have write/create permissions to directories used by the application, allowing them to create symbolic links or junctions
  4. Confirm application runs with elevated privileges
    In Task Manager, go to the Details tab, find the Password Manager process, and check the User Name column to verify if it runs as SYSTEM or another elevated account.
    Affected if The application process runs as SYSTEM or an administrator-level account while low-privileged users can manipulate symlinks in accessible paths

The environment is affected if the installed version is below 5.0.0.1270, the application is running with elevated (SYSTEM) privileges, AND low-privileged users have write access to directories where the application operates, enabling symlink/junction manipulation for privilege escalation.

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 5.0.0.1270 or later
Fixed in 5.0.0.1270
Interim mitigation

Update Trend Micro Password Manager to a version newer than 5.0.0.1266. As a compensating control, restrict file system permissions on directories accessible by the application to prevent low-privileged users from creating symlinks or junctions in those locations.

Recommended fix Moderate confidence

5.0.0.1270 or later

  1. 1. Check the current version of Trend Micro Password Manager installed on the system
  2. 2. Download the latest version (5.0.0.1270 or later) from the official Trend Micro support center at helpcenter.trendmicro.com
  3. 3. Uninstall the current version of Trend Micro Password Manager
  4. 4. Install the updated version 5.0.0.1270 or later
  5. 5. Verify the installation was successful and the version is now 5.0.0.1270 or higher

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

Fix this in Password Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30523 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-30523 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