Apex OneApplication · Trendmicro

CVE-2020-28582

MEDIUM · 5.3 CVSS v3.1 Published 2020-12-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
An improper access control information disclosure vulnerability in Trend Micro Apex One and OfficeScan XG SP1 could allow an unauthenticated user to connect to the product server and reveal number of managed agents.

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 confidence

An improper access control vulnerability in Trend Micro Apex One and OfficeScan XG SP1 allows unauthenticated remote attackers to connect to the product server and retrieve the number of managed endpoints/agents registered with the security solution. This information disclosure occurs due to missing authentication checks on a specific interface.

MitigationApply vendor-supplied patches for CVE-2020-28582. If patches are unavailable, restrict network access to the management interfaces using firewall rules or network segmentation to prevent unauthenticated access.

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
OfficescanApplication
Affected:= xg

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Trend Micro product and version
    Check the product version through the management console, registry key, or installed program information. For Apex One 2019 or OfficeScan XG, navigate to Help > About in the console, or check the version info in the Windows Control Panel under Programs.
    Affected if Version is Apex One 2019 or OfficeScan XG (any SP1 version)
  2. Verify network accessibility of the management interface
    Determine if the Apex One/OfficeScan web console (default ports 4343, 443) is exposed to the network or internet. Use a browser or curl to attempt access from an untrusted network location.
    Affected if The management console is reachable from untrusted network segments without VPN or firewall restrictions
  3. Check for unauthenticated access to the agent registration interface
    Attempt to access the suspected CGI interface that handles agent registration status. The vulnerability allows retrieval of the agent count without authentication. Observe if the request returns agent information without requiring login credentials.
    Affected if The interface returns endpoint/agent count or registration data without HTTP authentication or session cookies
  4. Review firewall and network segmentation configuration
    Inspect network firewall rules, perimeter firewall, or cloud security groups to determine if inbound access to the product ports (4343, 443, or custom management ports) is permitted from any external IP address.
    Affected if Inbound access to management ports is allowed from untrusted or public IP ranges without proper filtering

A system is affected if it runs Apex One 2019 or OfficeScan XG and the management interface with the vulnerable agent registration endpoint is network-accessible without authentication, allowing unauthenticated disclosure of managed endpoint counts.

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-supplied patches for CVE-2020-28582. If patches are unavailable, restrict network access to the management interfaces using firewall rules or network segmentation to prevent unauthenticated access.

Fix this in Apex One Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-28582 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