dbcve.org
Apex OneApplication · Trendmicro

CVE-2023-47194

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

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 to escalate privileges to SYSTEM level by exploiting improper validation of operation origins within the security agent's components.

MitigationApply the vendor-provided security patch for Apex One to address the origin validation flaw; verify that the security agent update does not conflict with existing endpoint protection policies.

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 if Trend Micro Apex One security agent is installed on the system - look for Apex One processes or service entries in the system registry or program list
    Affected if Apex One security agent is not installed on the endpoint
  2. Determine installed Apex One version
    Locate and read the installed version of Apex One - typically found in program files, registry keys, or via the security agent's built-in version information utility
    Affected if Cannot determine the installed version for comparison
  3. Compare version against affected range
    Compare your installed version number to the affected ranges: versions before 14.0.12737, or the 2019 release version
    Affected if Installed version is either before 14.0.12737 or matches the 2019 release (exact version 2019)
  4. Confirm security agent is active
    Verify the Apex One security agent components are running and loaded on the endpoint - check for active protection services
    Affected if The security agent is disabled or not running (the vulnerability requires the agent to be present and active)

You are affected if Apex One security agent is installed with a version before 14.0.12737 or is the 2019 release, and the security agent is active on the endpoint.

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-provided security patch for Apex One to address the origin validation flaw; verify that the security agent update does not conflict with existing endpoint protection policies.

Recommended fix Moderate confidence

Apex One version 14.0.12737 or later

  1. 1. Identify the current version of Trend Micro Apex One installed on the system
  2. 2. Navigate to the Trend Micro Apex One download center or contact Trend Micro support to obtain version 14.0.12737 or later
  3. 3. Download the appropriate installer for your Apex One version (either the standalone installer or the patch)
  4. 4. Apply the upgrade following Trend Micro's standard upgrade procedures
  5. 5. Verify the installation completed successfully and the version is 14.0.12737 or higher
  6. 6. Confirm the vulnerability is addressed by checking that the Apex One agent is running without errors
Caveat Standard upgrade considerations apply - test in non-production environment first, backup configuration, and ensure compatibility with existing infrastructure

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
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
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,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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