Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2020-24557: Local privilege escalation in Trend Micro endpoint security products

Published Sep 1, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS2.7%86th percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendor
Trend Micro
IdentifiersCVE-2020-24557CWE-284

CVE-2020-24557 is a local privilege-escalation vulnerability in Trend Micro endpoint security products on Microsoft Windows, including Apex One, Apex One as a Service, OfficeScan XG, and Worry-Free Business Security 10.0 SP1. The flaw involves logic controlling access to a product folder. An attacker who can already execute low-privileged code can manipulate that folder, temporarily disable security, and abuse Windows functionality to escalate privileges and execute code as SYSTEM. The vulnerability was patched in August 2020 and subsequently confirmed to have been exploited in multi-stage attacks.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can temporarily disable endpoint security features and elevate an attacker's existing low-privileged execution to SYSTEM-level code execution. Observed attacks used the vulnerability as a second-stage privilege-escalation mechanism rather than an initial compromise vector.

Mitigation

If you can’t patch tonight, do this now.

Microsoft Windows 10 version 1909, OS Build 18363.719, mitigates the hard-link behavior relevant to exploitation; earlier Windows versions are described as affected. This operating-system mitigation does not replace applying the affected product's security patches.

Remediation

Patch, then assume compromise.

Apply current vendor patches for the affected product. Identified affected releases include Apex One 2019 builds before 8422, Apex One as a Service builds before 202008, and OfficeScan versions before XG SP1 Build 5702. The historical remediation recommendations specify Apex One 2019 critical patches with builds later than 8422 and OfficeScan XG SP1 critical patches with builds later than 5702. Apex One as a Service received a fix through August 2020 maintenance. A specific fixed build for Worry-Free Business Security 10.0 SP1 is not available in the supplied information.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Trend MicroApex Oneapplication
Trend MicroWorry Free Business Securityapplication
FAQ

Frequently asked questions

Is CVE-2020-24557 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
Is there a public exploit for CVE-2020-24557?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2020-24557.
Is there a patch for CVE-2020-24557?
Apply current vendor patches for the affected product. Identified affected releases include Apex One 2019 builds before 8422, Apex One as a Service builds before 202008, and OfficeScan versions before XG SP1 Build 5702.
What products are affected by CVE-2020-24557?
Trend Micro Apex One and Trend Micro Worry Free Business Security.
How severe is CVE-2020-24557?
CVE-2020-24557 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 2.7% (86th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.