Threats / Trend Micro / CVE-2020-8599

CVE-2020-8599 · EUVD no mirror located · GCVE no mirror located Verified 2026-09-19

Trend Micro Apex One and OfficeScan vulnerability

Trend Micro Apex One and OfficeScan contain a vulnerable EXE file allowing remote attackers to write data to arbitrary paths and bypass root login authentication.

Verdict

Today item — known-exploited.

A remote code execution and authentication bypass vulnerability in Trend Micro endpoint protection products enables attackers to compromise server integrity without credentials. Active exploitation in the wild increases operational risk.

CISA KEV Yes · 2021-11-03⁴EPSS 0.11858 (verify live)⁵CVSS 9.8 (CISA)³CISA SSVC Exploitation: active · Automatable: yes · Impact: total³

Is it exploitable?

— the evidence, ranked above the score

Reported exploitation

1 independent public report of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.

cisa.gov ↗Confirmed

Exploited in the wild

Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03).

CISA KEV ↗Confirmed

Probability (EPSS)

EPSS 0.11858 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.

FIRST EPSS ↗High

Severity / affected

CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Trend Micro, Apex One and OfficeScan. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.

CISA-ADP ↗Reported

CISA SSVC (triage disposition)

Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.

CISA-ADP ↗Reported

Currency of the record

CISA added this to its KEV catalog 595 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.

CISA KEV ↗CVE.org ↗Reported

Who’s exploiting it?

— attribution turns risk into urgency

Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

Why it matters

— the attack path, told twice: adversary, then board

Front door — unauthenticated access narrative 1

Attacker

I identify the vulnerable EXE file exposed on the Trend Micro server.

Business

Endpoint protection infrastructure becomes a direct attack surface rather than a defensive layer.

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker

I send a crafted request to write malicious data to an arbitrary path on the server.

Business

System files or configurations are corrupted or replaced, degrading or disabling security controls.

Lateral reach — past segmentation narrative 3

Attacker

I bypass root authentication mechanisms to gain administrative access.

Business

Attackers obtain full control of the security management console and all protected endpoints.

What to do

— defensible action

Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.¹

Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.

Coverage & confidence

— what we know, and what we don’t

Established (cited)

KEV listing (CISA)

EPSS probability (FIRST)

1 reported-exploitation source(s)

CVSS 9.8 — CISA-assigned (CVE.org ADP)

CISA SSVC triage disposition (CVE.org ADP)

Catalogued by trendmicro (CNA)

Coverage gaps — stated, not hidden

No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.

EPSS & exposure are time-varying; verify live at the source.

Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.

No finder is named in the public CVE record — attribution scoped to the sources checked.

Disclosure & credit²

Catalogued by trendmicroCNA

Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.

Found an error? Propose a correction.

A correction is a cited counter-claim — it must cite a source, gets reviewed by a second human, and is never auto-applied. See the correction convention and our identity npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.

With JavaScript off: publish a signed kind 1111 Nostr event tagging ["r", "https://basicsecurity.net/threat/cve-2020-8599.html"], ["v", "sha256:fc09dedf0c95e627757a1fd8e27537a05d2ad6c9eb57f567a0bd04678b829640"] (the record version), plus ["src", "<your source URL>"] and ["t", "correction"], per the correction convention. Our identity: npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y. Cite-or-die: an event with no src is a coverage finding, not a proposal.