dbcve.org
Apex OneApplication · Trendmicro

CVE-2023-47196

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

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 the Trend Micro Apex One security agent allows a local attacker with low-privileged code execution to escalate to higher privileges. The vulnerability stems from improper validation of the origin of certain operations, likely in inter-process communication or file handling within the security agent.

MitigationApply the vendor-provided security patch for Apex One. Organizations should prioritize patching given the high CVSS score and the straightforward privilege escalation path for local attackers.

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 agent is installed
    Check for Trend Micro Apex One security agent installation on the system. This may be visible in installed programs list, or the product may have a visible icon in the system tray.
    Affected if The Apex One agent is present on the system
  2. Identify installed Apex One version
    Locate and read the installed version of the Apex One agent. This information is typically available in the agent UI, or through the product's about/version dialog, or via command-line tools provided by Trend Micro.
    Affected if The installed version number matches the affected ranges (less than 14.0.12737, or version 2019)
  3. Verify agent service is active
    Confirm the Apex One security agent service is currently running on the system. The vulnerability requires the security agent to be active and operational.
    Affected if The Apex One agent service is running and active on the system

A user is affected if the Apex One security agent is installed with a version less than 14.0.12737 (or version 2019) and the agent service is actively running on their 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-provided security patch for Apex One. Organizations should prioritize patching given the high CVSS score and the straightforward privilege escalation path for local attackers.

Recommended fix Moderate confidence

Apex One 14.0.12737 or later (or corresponding patch for 2019)

  1. Verify the current Apex One agent version on affected systems using the Apex One console or local system inspection
  2. Access the Trend Micro Download Center or your licensed portal to obtain the Apex One 14.0.12737 or later update
  3. In the Apex One management console, navigate to Updates > Agent. Select the affected agents or groups
  4. Deploy the agent update to upgrade from versions < 14.0.12737 to the fixed version
  5. After update deployment, verify the agent version has changed to 14.0.12737 or later to confirm remediation
  6. For Apex One 2019 specifically, apply the corresponding patch or upgrade path provided by Trend Micro for that version
Caveat Standard agent update - review Trend Micro release notes for any configuration or compatibility notes before deploying

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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