dbcve.org
Apex OneApplication · Trendmicro

CVE-2023-47198

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-47199.

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

An origin validation vulnerability in Trend Micro Apex One security agent allows a local attacker who has already achieved low-privileged code execution on the target system to escalate privileges to higher levels by bypassing origin checks in the agent's functionality.

MitigationApply the vendor patch for CVE-2023-47198 through the Trend Micro Apex One update mechanism; verify the patch version addresses the origin validation flaw.

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 Apex One installation
    Check for the presence of Trend Micro Apex One by looking for the installation directory (typically C:\Program Files\Trend Micro\Apex One) or check Windows Programs and Features for 'Trend Micro Apex One'
    Affected if Apex One is installed on the system
  2. Identify installed Apex One version
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\Apex One\CurrentVersion, or right-click the Apex One icon in the system tray and select 'About' to view the version number
    Affected if The displayed version is less than 14.0.12737 or equals 2019
  3. Confirm agent is active
    Verify the Apex One security agent service is running by opening Services.msc and checking for 'Trend Micro Apex One' or 'Apex One' service status, or check if the tray icon is present
    Affected if The agent service is running and the version is in the affected range

The system is affected if Trend Micro Apex One is installed with a version below 14.0.12737 or exactly version 2019, and the security agent is active.

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 patch for CVE-2023-47198 through the Trend Micro Apex One update mechanism; verify the patch version addresses the origin validation flaw.

Recommended fix Moderate confidence

Apex One version 14.0.12737 or later

  1. 1. Identify the current version of Apex One installed on the target system using the Apex One console or by checking the installed software details
  2. 2. Verify if the installed version is affected: versions below 14.0.12737 or version 2019 are vulnerable
  3. 3. Download Apex One version 14.0.12737 or later from the Trend Micro official download center or your licensed portal
  4. 4. Apply the upgrade following Trend Micro's standard upgrade procedures for Apex One agents
  5. 5. After upgrade, verify the new version is 14.0.12737 or higher and confirm the vulnerability is resolved
Caveat Review Trend Micro release notes for version 14.0.12737 to check for any configuration or feature changes that may require adjustment

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 / QA2.0 h
9.0 hours of engineering $1,620
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,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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