dbcve.org
Maximum Security 2022Application · Trendmicro

CVE-2024-32849

HIGH · 7.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 17.7 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 Security 17.x (Consumer) is vulnerable to a Privilege Escalation vulnerability that could allow a local attacker to unintentionally delete privileged Trend Micro files including its own.

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

Trend Micro Security 17.x consumer products contain a local privilege escalation vulnerability allowing an authenticated local attacker to delete privileged Trend Micro files, including the security software's own files. This likely stems from improper permission validation on file deletion operations within the security product.

MitigationApply the vendor patch or upgrade to a non-vulnerable version of Trend Micro Security (17.x and later). Organizations should identify any deployed instances of the vulnerable version and prioritize patching.

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
Maximum Security 2022Application
Affected:>= 17.0, < 17.7
Maximum Security 2023Application
Affected:>= 17.0, < 17.7

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. Verify Trend Micro Security installation
    Open Programs and Features (Windows) or check the application list to confirm a Trend Micro Security product is installed
    Affected if No Trend Micro Security product is found, the system is not affected by this specific vulnerability
  2. Identify the installed product name
    Locate the exact product name in the installed programs list, looking for 'Trend Micro Maximum Security 2022' or 'Trend Micro Maximum Security 2023'
    Affected if The product is not Maximum Security 2022 or 2023, this specific CVE does not apply
  3. Locate the installed version number
    Right-click the installed Trend Micro product in Programs and Features and select Properties, or check the product's About/Help section within the application
    Affected if Cannot determine the version number, manual verification required before proceeding
  4. Compare version against vulnerable range
    Check if the installed version is 17.0 or higher but lower than 17.7 (for example, 17.0, 17.5, 17.6.x)
    Affected if Version falls within >= 17.0 and < 17.7, the installed version is within the vulnerable range and the environment is affected

The environment is affected only if Trend Micro Maximum Security 2022 or 2023 is installed with a version between 17.0 and 17.6.x inclusive.

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

Apply the vendor patch or upgrade to a non-vulnerable version of Trend Micro Security (17.x and later). Organizations should identify any deployed instances of the vulnerable version and prioritize patching.

Recommended fix High confidence

Maximum Security 2022 or 2023 version 17.7 or later

  1. 1. Open Trend Micro Security 2022 or 2023 on the affected system
  2. 2. Navigate to Help > About or Settings > About to confirm the current version is below 17.7
  3. 3. Open a web browser and go to the official Trend Micro help center (helpcenter.trendmicro.com) or the official download page
  4. 4. Download Maximum Security version 17.7 or later for your product year (2022 or 2023)
  5. 5. Run the installer and follow the on-screen prompts to apply the security update
  6. 6. Restart the computer when prompted to complete the installation
  7. 7. Verify the installed version is now 17.7 or higher via Help > About

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

Fix this in Maximum Security 2022 Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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