dbcve.org
Apex OneApplication · Trendmicro

CVE-2023-47195

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

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 an origin validation vulnerability in the Trend Micro Apex One endpoint security agent that allows a local attacker with low-privileged code execution to escalate to higher (likely SYSTEM) privileges. The vulnerability stems from improper validation of the origin of requests or operations within the security agent's protected processes.

MitigationApply the vendor-supplied patch or update for Trend Micro Apex One when available. Until a patch is released, minimize the attack surface by restricting local code execution privileges and monitoring for suspicious process activity.

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
    Look for Trend Micro Apex One in installed programs or running processes on the system
    Affected if Apex One is installed and running
  2. Identify installed version
    Use the system's program information or Apex One's built-in version checker to obtain the exact version number
    Affected if Version is below 14.0.12737 or matches version 2019
  3. Verify low-privileged access exists
    Confirm the presence of a low-privileged user account or service with code execution capability on the system
    Affected if An unprivileged account or service with local code execution is present
  4. Check for suspicious privilege escalation
    Review process creation events, especially from lower-privileged processes spawning high-privilege Apex One-related processes
    Affected if Unexpected process creation patterns involving Apex One components are observed

A system is affected if Trend Micro Apex One is installed with a version below 14.0.12737 (or version 2019) AND an attacker already has low-privileged local code execution capability.

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 for Trend Micro Apex One when available. Until a patch is released, minimize the attack surface by restricting local code execution privileges and monitoring for suspicious process activity.

Recommended fix High confidence

Apex One version 14.0.12737 or later (including Apex One 2019 patched builds)

  1. 1. Identify current Apex One agent version by checking the installed software or using the Apex One console
  2. 2. Navigate to the Trend Micro Download Center or log into the Trend Micro Apex One management console
  3. 3. Download Apex One version 14.0.12737 or later (for Apex One 2019, download the corresponding patched build)
  4. 4. Review the Trend Micro installation/upgrade documentation before proceeding
  5. 5. Apply the upgrade through the Apex One central management console or by pushing the agent update to affected endpoints
  6. 6. Verify the upgrade was successful by checking the agent version number shows 14.0.12737 or higher
  7. 7. Confirm the Apex One services are running properly after the update
Caveat Standard upgrade risks apply - test in a staging environment first, ensure backup of configuration exists, and verify compatibility with other security solutions in the environment

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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