dbcve.org
Apex OneApplication · Trendmicro

CVE-2023-47200

HIGH · 7.8 CVSS v3.1 Published 2024-01-23
Fix available
A fix is available. Upgrade to 14.0.12737 or later.
See remediation →
80/100
Remediation priority · High
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
A plug-in manager origin validation vulnerability in the Trend Micro Apex One security agent 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. This vulnerability is similar to, but not identical to, CVE-2023-47201.

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

A plug-in manager origin validation vulnerability in Trend Micro Apex One security agent allows local attackers with existing low-privileged code execution to escalate privileges by exploiting improper validation of plug-in origins, bypassing normal security checks in the plug-in manager component.

MitigationApply the vendor-supplied security patch for Apex One immediately; prioritize patching endpoints where untrusted users or code may have access, as the vulnerability requires low-privileged execution as an attack prerequisite.

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:< 14.0.12737= 2019

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
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 checks

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

  1. Confirm Apex One installation
    Locate the Trend Micro Apex One security agent installation on the endpoint (typically in Program Files or Program Files (x86) under Trend Micro).
    Affected if Apex One is not installed on the system.
  2. Identify installed Apex One version
    Use the system registry or Apex One client interface to retrieve the exact version number of the installed security agent.
    Affected if The installed version is either (a) lower than 14.0.12737, or (b) identified as version 2019.
  3. Verify plug-in manager component
    Confirm the plug-in manager component is present and active on the endpoint as part of the Apex One installation.
    Affected if The plug-in manager component is not present or has been removed.
  4. Check for existing low-privileged access
    Review system for any unauthorized or unexpected low-privilege processes or user accounts that may indicate the prerequisite for this attack exists.
    Affected if Untrusted low-privileged code execution or unauthorized user access is detected on the system.

The system is affected by this vulnerability if Apex One is installed with a version below 14.0.12737 (or version 2019) and the plug-in manager component is present, allowing a local attacker with low-privileged code execution to potentially escalate privileges.

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.

dbcve · scoped
Upgrade available Upgrade to 14.0.12737 or later
Fixed in 14.0.12737
Interim mitigation

Apply the vendor-supplied security patch for Apex One immediately; prioritize patching endpoints where untrusted users or code may have access, as the vulnerability requires low-privileged execution as an attack prerequisite.

Recommended fix High confidence

Apex One version 14.0.12737 or later

  1. Verify current Apex One agent version by checking the installed software or using the Apex One console
  2. Download Apex One version 14.0.12737 or later from the Trend Micro Download Center
  3. Test the upgrade in a non-production environment first
  4. Apply the update through the Apex One central management console or via automated deployment
  5. Verify successful installation by checking the agent version post-update
  6. Confirm the plug-in manager component is updated to the fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apex One Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47200 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2023-47200 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