dbcve.org
Apex OneApplication · Trendmicro

CVE-2023-47192

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 agent link 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.

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. An attacker who has already achieved low-privileged code execution on the target system can exploit an agent link vulnerability to elevate their privileges to a higher level, potentially gaining SYSTEM or administrative access.

MitigationApply the vendor-supplied patch or update Trend Micro Apex One to the latest version to remediate this 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. Verify Trend Micro Apex One is installed
    Check for Apex One installation by looking in Program Files for 'Trend Micro' or 'Apex One' folder, or query the Windows Registry at HKLM\SOFTWARE\TrendMicro for Apex One keys
    Affected if Apex One is not found on the system, then the vulnerability does not apply
  2. Identify installed Apex One version
    Open the Apex One console and navigate to Help > About, or check the registry key HKLM\SOFTWARE\TrendMicro\Apex One\CurrentVersion for the value of 'Server_Version' or 'Version'
    Affected if The version returned is lower than 14.0.12737 or equals 2019 (e.g., 2019, 14.0.x before 14.0.12737)
  3. Confirm agent link vulnerability component is enabled
    Check if the Apex One agent communication feature or 'Agent Link' service is active by examining services.msc for 'Trend Micro Apex One' related services, or check the configuration file 'ofcscan.ini' for AgentLink settings under the [odule_AgentLink] section
    Affected if The agent link component is enabled and the installed version is within the affected range

A system is affected if Trend Micro Apex One is installed with a version lower than 14.0.12737 or exactly version 2019, and the agent link vulnerability component is present and enabled on the target system.

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 Trend Micro Apex One to the latest version to remediate this vulnerability.

Recommended fix Moderate confidence

Apex One Security Agent version 14.0.12737 or later

  1. 1. Identify the current installed version of Trend Micro Apex One security agent on affected systems
  2. 2. Navigate to the Trend Micro Download Center or access the Patch Download section of your Apex One management console
  3. 3. Download Apex One Security Agent version 14.0.12737 or later for all affected endpoints
  4. 4. Deploy the security agent update through the Apex One management console, or manually install on each affected system
  5. 5. Verify the installation was successful by checking the agent version number
  6. 6. Restart the security agent services if required to ensure the patch takes effect
Caveat Standard patch deployment considerations apply - test in a non-production environment first

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

Fix this in Apex One Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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