Antivirus OneApplication · Trendmicro

CVE-2024-45334

HIGH · 7.8 CVSS v3.1 Published 2024-10-22
Fix available
A fix is available. Upgrade to 3.10.6 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 Antivirus One versions 3.10.4 and below (Consumer) is vulnerable to an Arbitrary Configuration Update that could allow unauthorized access to product configurations and functions.

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 Antivirus One versions 3.10.4 and below contains a vulnerability that allows arbitrary (unauthorized) configuration updates. This could permit an attacker to modify product settings and access functions beyond their intended permissions, potentially weakening security controls or enabling further exploitation.

MitigationUpgrade to a version of Trend Micro Antivirus One above 3.10.4 once the vendor releases a patch. Monitor vendor advisories for the official fixed version and apply updates promptly.

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
Antivirus OneApplication
Affected:< 3.10.6

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 Antivirus One installation
    Check system for installed Trend Micro Antivirus One software - look in program files, registry uninstall entries, or use system inventory tools
    Affected if Trend Micro Antivirus One is found installed on the system
  2. Determine installed version
    Locate and read the installed version information for Trend Micro Antivirus One - typically available in program properties, about dialog, or registry
    Affected if Installed version is below 3.10.6 (versions 3.10.4 and below are confirmed vulnerable)
  3. Check for remote management features
    Inspect product settings for remote management, remote configuration, or cloud-based management features that accept configuration inputs
    Affected if Remote management or configuration update features are enabled and accessible without proper authentication
  4. Review recent configuration changes
    Examine product configuration logs, audit trails, or configuration history for unauthorized or unexpected setting modifications
    Affected if Configuration changes exist that were not initiated by an authorized administrator

A system is affected if Trend Micro Antivirus One version 3.10.4 or below is installed with remote or unauthenticated configuration update capabilities accessible to unauthorized users.

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.10.6 or later
Fixed in 3.10.6
Interim mitigation

Upgrade to a version of Trend Micro Antivirus One above 3.10.4 once the vendor releases a patch. Monitor vendor advisories for the official fixed version and apply updates promptly.

Recommended fix High confidence

Antivirus One version 3.10.6 or later

  1. Navigate to the Trend Micro Antivirus One application on your device
  2. Check the current version by going to Settings > About or Help > About
  3. Download the latest version (3.10.6 or higher) from the official Trend Micro website or through the application's built-in update feature
  4. Run the installer and follow the prompts to complete the upgrade
  5. Restart the application if prompted and verify the version has been updated to 3.10.6 or later

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

Fix this in Antivirus One Scoped from the published advisory
  • Consultation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,280
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,048.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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