dbcve.org
Apex OneApplication · Trendmicro

CVE-2023-47197

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

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 by exploiting improper validation of operation origins within the security agent's functionality.

MitigationApply the vendor-supplied patch for CVE-2023-47197 to affected Apex One installations; until patch deployment, limit local access to trusted personnel only.

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
    Verify if Trend Micro Apex One security agent is installed on the system using system inventory tools, program listings, or running services
    Affected if Apex One is not installed on the system
  2. Determine installed version
    Retrieve the exact installed version of Apex One through the product's built-in version information, system registry, or management console
    Affected if Unable to determine the installed version
  3. Compare against vulnerable version ranges
    Compare the detected version against the affected ranges: versions lower than 14.0.12737 or version 2019
    Affected if Installed version is less than 14.0.12737 or equals 2019
  4. Identify low-privileged access scenario
    Determine whether low-privileged users have the ability to execute code or access Apex One components on the system
    Affected if Low-privileged code execution capability exists alongside vulnerable Apex One version

System is affected if Apex One is installed and the version is below 14.0.12737 or is exactly version 2019, allowing a low-privileged attacker to exploit origin validation for privilege escalation.

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 for CVE-2023-47197 to affected Apex One installations; until patch deployment, limit local access to trusted personnel only.

Recommended fix High confidence

Apex One version 14.0.12737 or later

  1. Identify the current installed version of Trend Micro Apex One on the target system
  2. Navigate to the official Trend Micro download portal or contact Trend Micro customer support
  3. Download Apex One version 14.0.12737 or later
  4. Before upgrading, ensure all pending tasks and scheduled scans are stopped
  5. Create a full backup of the current Apex One configuration and policy settings
  6. Apply the upgrade following Trend Micro's standard upgrade procedure for Apex One agents
  7. Verify the upgrade was successful by checking the installed version number
  8. Confirm the Apex One service is running correctly after upgrade
Caveat Standard upgrade considerations apply - test in non-production environment first, ensure compatibility with existing infrastructure, and back up configuration before proceeding

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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