Password ManagerApplication · Trendmicro

CVE-2021-32461

HIGH · 7.8 CVSS v3.1 Published 2021-07-08
Fix available
A fix is available. Upgrade to after 5.0.0.1217 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.1217 and below is vulnerable to an Integer Truncation Privilege Escalation vulnerability which could allow a local attacker to trigger a buffer overflow and escalate privileges on affected installations. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.

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

Trend Micro Password Manager versions 5.0.0.1217 and below contains an integer truncation flaw that can be exploited to trigger a buffer overflow, allowing a local attacker who already has low-privileged code execution to escalate to SYSTEM privileges on affected Windows installations.

MitigationUpdate Trend Micro Password Manager to a version newer than 5.0.0.1217 or apply the vendor-supplied patch to remediate the integer truncation vulnerability.

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.1217

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. Confirm Trend Micro Password Manager installation
    Open Control Panel > Programs and Features, or check for the presence of Trend Micro Password Manager in the program list. Alternatively, search for 'Trend Micro Password Manager' in the Start menu.
    Affected if The program is listed as installed on the system
  2. Identify installed version number
    Right-click on Trend Micro Password Manager in Programs and Features and select 'Properties', or right-click the application shortcut and select 'Properties' to view the Version field. The version appears as '5.0.0.xxxx' or similar.
    Affected if The version displayed is 5.0.0.1217 or any version number lower than 5.0.0.1217
  3. Verify version against CVE-affected range
    Compare the identified version number to the affected range. Versions 5.0.0.1217 and below are vulnerable. Note that only the Windows version of Trend Micro Password Manager is affected by this CVE.
    Affected if The installed version is 5.0.0.1217 or any version listed as 5.0.0.xxxx where xxxx is less than or equal to 1217
  4. Check if low-privileged code execution is possible
    This CVE requires an attacker to already have low-privileged code execution on the system to escalate to SYSTEM privileges. Review user access controls and application isolation policies.
    Affected if The system allows low-privileged users to execute code and the vulnerable software is installed

The environment is affected if Trend Micro Password Manager version 5.0.0.1217 or lower is installed on a Windows system, as the integer truncation vulnerability can then be exploited for local 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.

From vendor data
Upgrade available Upgrade to a release after 5.0.0.1217
Interim mitigation

Update Trend Micro Password Manager to a version newer than 5.0.0.1217 or apply the vendor-supplied patch to remediate the integer truncation vulnerability.

Fix this in Password Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-32461 — 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-2021-32461 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