dbcve.org
Apex OneApplication · Trendmicro

CVE-2024-36302

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 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-2024-36303.

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 security agent that allows a local attacker with low-privileged code execution to escalate privileges to higher levels on affected installations. The vulnerability stems from improper validation of the origin of requests or operations, enabling privilege escalation.

MitigationApply the vendor patch from Trend Micro when available. In the interim, limit user privileges and restrict the ability to execute low-privileged code on affected systems to reduce the attack surface.

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 agent is installed
    Check for the presence of Apex One by looking for its installation directory (typically C:\Program Files\Trend Micro\Apex One\) or by querying the Windows Registry under HKLM\SOFTWARE\TrendMicro\Apex One
    Affected if Apex One is not found on the system, then this CVE does not apply
  2. Identify installed Apex One version
    Run the command '"C:\Program Files\Trend Micro\Apex One\ofcscan.ini"' or check the Windows Registry key HKLM\SOFTWARE\TrendMicro\Apex One\CurrentVersion for the value 'Server_Version' or 'NTRtsk_Version'
    Affected if The displayed version falls within the affected ranges: any version below 14.0.13139, or version 14.0.x where x is less than 12980
  3. Confirm the affected component is active
    Verify the Apex One security agent service is running by checking the 'Trend Micro Apex One NT Listener' service status via 'services.msc' or the command 'sc query 'Tmlisten''
    Affected if The service is running and the version is within the affected ranges listed above
  4. Check for low-privileged user access
    Verify that the system has user accounts with limited privileges who could potentially exploit this flaw. Use 'net user' or check local group memberships to identify non-admin users
    Affected if Low-privileged users exist on the system and Apex One version is within the affected ranges, indicating the privilege escalation path could be exploited

A system is affected if Trend Micro Apex One is installed with a version below 14.0.13139 (or 14.0.x versions below 12980) and the agent service is active, allowing a low-privileged local user to potentially escalate privileges.

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 patch from Trend Micro when available. In the interim, limit user privileges and restrict the ability to execute low-privileged code on affected systems to reduce the attack surface.

Recommended fix Moderate confidence

Apex One version 14.0.13139 or later

  1. 1. Verify the current installed version of Trend Micro Apex One security agent by checking the product About or version information.
  2. 2. Navigate to the Trend Micro Download Center or log into the Trend Micro Customer Support Portal.
  3. 3. Download the latest Apex One security agent version or version 14.0.13139 (or later) which contains the security fix for CVE-2024-36302.
  4. 4. Before applying the update, ensure appropriate backups or system snapshots are in place.
  5. 5. Apply the security update following Trend Micro's standard upgrade procedures for Apex One agents.
  6. 6. Verify the installation completed successfully and confirm the new version is reflected in the product UI.
  7. 7. Test that normal Apex One functionality (real-time protection, scanning, updates) continues to operate correctly.
Caveat Review release notes for version 14.0.13139 for any changes to functionality or compatibility requirements before upgrading

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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