CVE-2020-28577
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 · uneditedAn 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 server hostname and db names.
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 confidenceThis improper access control vulnerability in Trend Micro Apex One and OfficeScan XG SP1 allows unauthenticated users to connect to the product server and retrieve sensitive system information including the server hostname and database names. The CVSS 5.3 score reflects the information disclosure's moderate impact on reconnaissance for further attacks.
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= 2019= xgCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Trend Micro product and versionCheck the installed product version through the management console or system information. For Apex One, look for version 2019. For OfficeScan, look for version XG with SP1.Affected if The installed version is Apex One 2019 or OfficeScan XG SP1.
-
Verify if the management interface is network accessibleDetermine if the Apex One/OfficeScan web management console is accessible from network locations. Check firewall rules and network segmentation around the server hosting the product.Affected if The management interface is reachable from untrusted network segments or the internet.
-
Test for unauthenticated information disclosureAttempt to access the vulnerable endpoint without credentials. Send an HTTP request to the product server looking for system information disclosure without authentication. The exact endpoint varies by configuration but typically involves the product's web services.Affected if Sensitive system information such as server hostname and database names can be retrieved without any authentication credentials.
-
Review network access controlsExamine the network access control list or firewall rules governing access to the Apex One/OfficeScan management port (typically ports 4343, 443, or 8080).Affected if The management interface allows connections from IP addresses that are not trusted or are outside the organization.
A system is affected if it runs Apex One 2019 or OfficeScan XG SP1 and has its management interface accessible to untrusted network sources without proper authentication controls.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor-released security patches for Apex One and OfficeScan XG SP1 to address the improper access control. Restrict network access to the management interface to trusted IP addresses as a compensating control until the patch is applied.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28577 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-28577 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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