dbcve.org
Apex OneApplication · Trendmicro

CVE-2024-37289

HIGH · 7.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 14.0.0.12980 / 14.0.13139 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 improper access control vulnerability in Trend Micro Apex One 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.

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 improper access control vulnerability in Trend Micro Apex One that allows a local attacker who has already obtained low-privileged code execution on the target system to escalate privileges to higher levels, potentially gaining administrative or system-level access.

MitigationApply the vendor-supplied security patch or update to Trend Micro Apex One to remediate the improper access control 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.13139>= 14.0, < 14.0.0.12980

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 is installed
    Check if Trend Micro Apex One is present on the system. Look for the installation directory at C:\Program Files\Trend Micro\Apex One\, or check Windows Services for the 'Apex One' service, or check Windows Programs and Features for Trend Micro Apex One.
    Affected if If Apex One is not installed, this CVE does not apply to the system.
  2. Determine the installed Apex One version
    Retrieve the installed version number. Check the Windows registry key HKLM\SOFTWARE\TrendMicro\Apex One\CurrentVersion\Version, or right-click the Apex One system tray icon and select 'About' or 'Product Information' to view the version.
    Affected if The exact version number is required to determine vulnerability status.
  3. Compare version to affected ranges
    Compare the installed version against the affected ranges: version 14.0 through 14.0.0.12979, or any version lower than 14.0.13139. Note that 14.0.0.12980 and later versions, as well as 14.0.13139 and later versions, are not affected.
    Affected if If the installed version is 14.0.0.12979 or lower, or any version below 14.0.13139, the system is affected by this improper access control vulnerability.

The system is affected if Trend Micro Apex One is installed and the installed version falls within 14.0 <= version < 14.0.0.12980 or version < 14.0.13139, as these versions contain the improper access control flaw allowing local 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.0.12980 / 14.0.13139 or later
Fixed in 14.0.0.1298014.0.13139
Interim mitigation

Apply the vendor-supplied security patch or update to Trend Micro Apex One to remediate the improper access control flaw.

Recommended fix Moderate confidence

Upgrade to Apex One version 14.0.13139 or later, or version 14.0.0.12980 or later

  1. 1. Identify the current installed version of Trend Micro Apex One on the system
  2. 2. Navigate to the Trend Micro Apex One product console or use the built-in version checker
  3. 3. Download the latest security patch or hotfix from the Trend Micro customer support portal (success.trendmicro.com)
  4. 4. Apply the update following Trend Micro's standard patch deployment procedures
  5. 5. Verify the installation was successful by confirming the version reflects 14.0.13139 or higher, or 14.0.0.12980 or higher
  6. 6. Restart the Apex One services if required by the update
Caveat Review release notes for any compatibility considerations or changes to agent functionality before deploying in production environments

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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