CVE-2023-47202
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 · uneditedA local file inclusion vulnerability on the Trend Micro Apex One management server could allow a local attacker to escalate privileges on affected installations. Please note: an attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.
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 confidenceA local file inclusion vulnerability in Trend Micro Apex One management server allows an attacker who has already achieved low-privileged code execution on the system to manipulate file path references and gain elevated (administrator/root) privileges. The vulnerability stems from insufficient validation of user-supplied file path parameters.
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< 14.0.12737= 2019CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 if Apex One is installedCheck for the presence of Apex One by looking for its installation directory (commonly at C:\Program Files\Trend Micro\Apex One or C:\Program Files (x86)\Trend Micro\Apex One on Windows, or /opt/ApexOne on Linux), or by checking for the 'Apex One' service in Windows Services or running processes.Affected if Apex One is not installed on the system
-
Determine installed Apex One versionOn Windows, check the version by viewing the file properties of the main executable (often at C:\Program Files\Trend Micro\Apex One\coreFramework\PCCSRV\.exe or similar), or check the registry key HKLM\SOFTWARE\TrendMicro\Apex One\CurrentVersion. On Linux, check /opt/ApexOne/version.ini or similar version file.Affected if The installed version number cannot be determined or is not visible
-
Compare version against affected rangeTake the installed version number (such as 14.0.xxxx) and compare it to the affected range: versions less than 14.0.12737, or version 2019 (regardless of build number), are vulnerable.Affected if Installed version is less than 14.0.12737, or the version string contains '2019'
-
Verify management interface accessibilityCheck if the Apex One web management console is accessible on port 4343 (default HTTPS) or port 8080. This is the component that processes the file path parameters. Check network listeners or firewall rules.Affected if The management interface is accessible from untrusted networks (not just localhost or admin VLAN)
-
Review for indicators of low-privileged accessSince this vulnerability requires an attacker to already have low-privileged code execution, audit system logs (Windows Event Logs or Linux auth.log) for any suspicious processes or accounts that may indicate prior compromise, and check for unexpected user accounts or modified service configurations.Affected if Evidence exists of prior low-privileged code execution or unauthorized access to the system
A system is affected if Apex One is installed with version less than 14.0.12737 or version 2019, and the attacker already has low-privileged code execution on the system to manipulate file path parameters in the management interface.
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.
dbcve · scoped14.0.12737
Apply the vendor-supplied security patch for CVE-2023-47202. Additionally, limit server access to trusted administrators only, and implement least-privilege principles to reduce the impact of initial compromise.
Apex One version 14.0.12737 or later
- 1. Back up the current Apex One installation and configuration before proceeding with any upgrade.
- 2. Download the latest Apex One version from the Trend Micro download center or your licensed portal.
- 3. Ensure the system meets the prerequisites for the new version installation.
- 4. Apply the upgrade following Trend Micro's standard upgrade procedures for Apex One management server.
- 5. After upgrade, verify that the version is 14.0.12737 or later.
- 6. Test that normal Apex One functionality is working after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47202 — 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-2023-47202 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