CVE-2024-45335
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 · uneditedTrend Micro Antivirus One, version 3.10.4 and below contains a vulnerability that could allow an attacker to use a specifically crafted virus to allow itself to bypass and evade a virus scan detection.
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 confidenceThis is an antivirus evasion vulnerability in Trend Micro Antivirus One version 3.10.4 and below. Specifically crafted malware can bypass the virus scanning engine and evade detection, allowing malicious files to pass through without being flagged as threats.
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< 3.10.6CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Trend Micro Antivirus One is installedCheck for the product in installed programs: On Windows, open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell. Look for 'Trend Micro Antivirus One' in the list.Affected if The product is not listed in installed programs
-
Determine installed version numberIf Trend Micro Antivirus One is found, note the DisplayVersion value from the registry or program list. Alternatively, right-click the tray icon and select 'About' or open the main interface and navigate to Settings > About to view the version.Affected if The version displayed is 3.10.5, 3.10.4, or lower (any version below 3.10.6)
-
Confirm real-time protection is activeOpen the Trend Micro Antivirus One main interface and verify that real-time scanning or virus shield is enabled. This is typically found under 'Settings' > 'Protection' or a similar menu option showing the current protection status.Affected if Real-time protection is enabled and the installed version is below 3.10.6 - the evasion would apply to files scanned in real-time
The environment is affected if Trend Micro Antivirus One version 3.10.5 or below is installed with active real-time scanning, as crafted malware could bypass detection.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.10.6
Update Trend Micro Antivirus One to a version newer than 3.10.4 once the vendor releases a patch to address this evasion technique. Ensure regular signature and engine updates are applied.
Version 3.10.6 or later
- Check the current installed version of Trend Micro Antivirus One
- Download Trend Micro Antivirus One version 3.10.6 or later from the official Trend Micro website or helpcenter.trendmicro.com
- Install the updated version following the standard installation process
- Restart the application if required and verify the new version is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45335 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45335 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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