dbcve.org
Apex OneApplication · Trendmicro

CVE-2023-47199

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
An 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-47193.

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

This is a local privilege escalation vulnerability in Trend Micro Apex One security agent stemming from improper origin validation. An attacker with low-privileged code execution can exploit this flaw to elevate to higher privileges, likely by manipulating inter-process communication or requests that the security agent fails to properly validate for origin trustworthiness.

MitigationApply the vendor-supplied patch or update to the latest version of Trend Micro Apex One to address this origin validation vulnerability.

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. Identify Apex One agent installation
    Locate the Trend Micro Apex One security agent on the system. Check for installation directory (commonly C:\Program Files\Trend Micro\ or C:\Program Files (x86)\Trend Micro\) or use system inventory tools to find the product.
    Affected if The Apex One security agent is installed on the system.
  2. Determine installed version
    Access the Apex One agent version information. This is typically available via the agent UI (right-click the system tray icon and select 'About'), through the registry at HKLM\SOFTWARE\TrendMicro\Apex One, or by running the agent's version command if available.
    Affected if The installed version is below 14.0.12737 or matches the 2019 release version.
  3. Confirm security agent service is active
    Verify the Apex One security agent service is running. Check Windows Services (services.msc) for 'Apex One' or 'Trend Micro Apex One' service, or query via command: sc query 'Apex One service name'
    Affected if The security agent service is actively running on the system.
  4. Check for low-privileged code execution context
    Review system access and permissions. Determine if unprivileged users or processes can interact with the Apex One agent's inter-process communication mechanisms.
    Affected if Low-privileged users or processes have the ability to send requests or commands to the Apex One security agent.

A system is affected if Trend Micro Apex One security agent is installed with a version below 14.0.12737 (or the 2019 version) and the agent service is running, allowing unprivileged users to potentially manipulate IPC requests.

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 patch or update to the latest version of Trend Micro Apex One to address this origin validation vulnerability.

Recommended fix Moderate confidence

14.0.12737 or later

  1. 1. Identify the current version of Apex One security agent installed on the target system
  2. 2. Obtain the fixed version (14.0.12737 or later) from Trend Micro's official support portal or authorized download channels
  3. 3. Follow Trend Micro's standard upgrade procedure for Apex One security agent - this typically involves running the installer with appropriate administrative privileges
  4. 4. Verify the installation completed successfully
  5. 5. Confirm the installed version is now 14.0.12737 or higher

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

Fix this in Apex One Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47199 — 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-47199 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