Safeguard
Vulnerability Analysis

CVE-2020-24557: Trend Micro Multiple Products Improper Access Control Vulnerability

CVE-2020-24557 affects Trend Micro Apex One, OfficeScan, and Worry-Free Business Security and is listed in CISA's Known Exploited Vulnerabilities catalog, meaning exploitation has been observed in the wild. Added 2021-11-03.

Safeguard Research Team
3 min read

CVE-2020-24557: Trend Micro Multiple Products Improper Access Control Vulnerability

Status: confirmed exploited in the wild

CVE-2020-24557 appears in CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2021-11-03. Inclusion in KEV is not a severity prediction. It means CISA has reliable evidence that the vulnerability has actually been exploited against real targets, which is a stronger signal than a CVSS score on its own.

FieldValue
CVECVE-2020-24557
VendorTrend Micro
ProductApex One, OfficeScan, and Worry-Free Business Security
Added to KEV2021-11-03
Federal due date2022-05-03
Ransomware campaign useUnknown

What the vulnerability is

Trend Micro Apex One, OfficeScan, and Worry-Free Business Security on Microsoft Windows contain an improper access control vulnerability that may allow an attacker to manipulate a particular product folder to disable the security temporarily, abuse a specific Windows function, and attain privilege escalation.

Weakness classification

CISA does not record a CWE classification for this entry.

Required action

CISA's stated required action for this entry:

Apply updates per vendor instructions.

Ransomware context

CISA lists ransomware campaign use for this entry as "Unknown". That is an absence of confirmation rather than evidence it has not been used, so it should not be read as lowering priority.

Federal remediation deadline

Under CISA Binding Operational Directive 22-01, U.S. federal civilian executive branch agencies were required to remediate this vulnerability by 2022-05-03. The directive does not bind private organisations, but the due date is a useful external signal: CISA sets shorter windows for what it assesses as higher risk.

Why KEV membership changes prioritisation

Most vulnerability backlogs are too large to clear, so the practical question is ordering rather than coverage. KEV is useful for that because it is evidence-based: an entry is on the list because exploitation was observed, not because a scoring formula predicted it might be.

A defensible triage rule used widely is to treat KEV membership as a promotion signal that overrides CVSS ranking, on the basis that a confirmed-exploited medium-severity issue generally warrants attention ahead of a theoretical critical one.

Determining whether you are affected

  1. Establish whether Trend Micro Apex One, OfficeScan, and Worry-Free Business Security is present anywhere in your estate, including indirectly and in systems not under active management.
  2. Identify the deployed versions and compare against the vendor advisory linked below.
  3. Apply the required action above, then confirm the change took effect rather than assuming it did.

Step one is where this usually fails. Several of the most costly incidents on record, including Code Red and Log4Shell, turned on organisations being unable to answer whether affected software was present at all.

How Safeguard helps

Safeguard's vulnerability management enriches findings with KEV and EPSS data, so an entry like this one surfaces as confirmed-exploited rather than sitting undifferentiated in a ranked list.

Sources

Catalog data retrieved from CISA KEV version 2026.09.16. Verify against the live catalog before relying on dates for compliance purposes.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.