dbcve.org
Apex OneApplication · Trendmicro

CVE-2020-24558

HIGH · 7.1 CVSS v3.1 Published 2020-09-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
A vulnerability in an Trend Micro Apex One, Worry-Free Business Security 10.0 SP1 and Worry-Free Business Security Services dll may allow an attacker to manipulate it to cause an out-of-bounds read that crashes multiple processes in the product. 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

A vulnerability in a Trend Micro DLL allows an attacker with low-privileged code execution to manipulate the DLL, triggering an out-of-bounds read that crashes multiple processes in Apex One, Worry-Free Business Security 10.0 SP1, and Worry-Free Business Security Services. This constitutes a local denial-of-service vulnerability requiring prior code execution capability.

MitigationApply vendor patches from Trend Micro for affected products and restrict low-privileged code execution capabilities on endpoints where possible.

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
Apex OneApplication
Affected:= 2019= saas
Worry Free Business SecurityApplication
Affected:= 10.0
Worry Free Business Security ServicesApplication
Affected:all versions

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
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 security product
    Open Control Panel > Programs and Features, or run: Get-WmiObject -Class Win32_Product to list installed software. Look for 'Trend Micro Apex One', 'Trend Micro Worry-Free Business Security', or 'Trend Micro Worry-Free Business Security Services'.
    Affected if Any of these three Trend Micro products are installed on the system.
  2. Check Apex One version
    Open the Apex One console, or check registry key: HKLM\SOFTWARE\Trend Micro\Apex One\Installer\Version. Compare the installed version to 2019 or 'saas' variants.
    Affected if Apex One version is 2019 or the SaaS deployment model.
  3. Check Worry-Free Business Security version
    Open the WFBS console, or check registry key: HKLM\SOFTWARE\Trend Micro\Worry-Free Business Security\CurrentVersion\InstallPath. Compare version to 10.0 SP1.
    Affected if Worry-Free Business Security version is 10.0 (specifically SP1).
  4. Check Worry-Free Business Security Services status
    Verify if the system is enrolled in Worry-Free Business Security Services (cloud-managed). This is typically visible in the Trend Micro Central Reporting console or via the installed agent properties.
    Affected if The system is running Worry-Free Business Security Services (all versions).
  5. Confirm low-privileged code execution exposure
    Review local user accounts and group memberships (via Computer Management > Local Users and Groups or 'net user' command). Determine if untrusted or low-privileged users have the ability to execute code on the endpoint.
    Affected if Low-privileged or untrusted users can execute code on the affected system, which is required for this DoS to be exploited.

The system is affected if any Trend Micro product from the list is installed AND the specific version matches the affected ranges, AND an attacker with low-privileged code execution access exists on that endpoint.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches from Trend Micro for affected products and restrict low-privileged code execution capabilities on endpoints where possible.

Fix this in Apex One Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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