dbcve.org
Apex OneApplication · Trendmicro

CVE-2024-55917

HIGH · 7.8 CVSS v3.1 Published 2024-12-31
Fix available
A fix is available. Upgrade to 14.0.14203 / 2019.13140 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 error 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 a local privilege escalation vulnerability in Trend Micro Apex One endpoint protection software. The origin validation error allows an attacker who has already achieved low-privileged code execution on the target system to elevate to higher (administrator/system) privileges. This type of flaw typically involves improper verification of the source or context of a request/operation, enabling attackers to bypass intended access controls.

MitigationApply the vendor patch or security update released by Trend Micro for Apex One. Organizations should prioritize patching endpoints given the requirement for prior code execution and the high severity rating.

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.14203< 2019.13140

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. Check if Trend Micro Apex One is installed
    Open Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Select-Object Name,Version' in PowerShell, or check for the service 'Apex One' in Services.msc
    Affected if Apex One endpoint protection software is present on the system
  2. Identify the installed Apex One version
    Check the registry key at HKLM\SOFTWARE\TrendMicro\Apex One\CurrentVersion for value 'Server_Version' or 'Version', or check the file version of 'Apex One.exe' in the installation directory (typically C:\Program Files\Trend Micro\Apex One\)
    Affected if The version number is lower than 14.0.14203 or, for legacy builds, lower than 2019.13140
  3. Verify the component serving client connections
    If using SaaS or agent mode, check the running process 'TmCCSF.exe' or 'NCTSS.exe' and verify its file version via right-click > Properties > Details
    Affected if The component version matches a vulnerable Apex One release below the patched builds

The system is affected if Trend Micro Apex One is installed and the installed version falls below 14.0.14203 (or 2019.13140 for the 2019 branch), since the privilege escalation flaw exists in those unpatched versions.

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.14203 / 2019.13140 or later
Fixed in 14.0.142032019.13140
Interim mitigation

Apply the vendor patch or security update released by Trend Micro for Apex One. Organizations should prioritize patching endpoints given the requirement for prior code execution and the high severity rating.

Recommended fix Moderate confidence

Upgrade to Apex One 14.0.14203 (or later 14.x release) OR Apex One 2019.13140 (or later 2019 release)

  1. 1. Identify the current version of Apex One by checking the product console or system information
  2. 2. Navigate to the Trend Micro Download Center or contact Trend Micro Customer Support to obtain the fixed version (14.0.14203 or later for the 14.x branch, or 2019.13140 or later for the 2019 branch)
  3. 3. Review the Apex One upgrade documentation for your specific version branch
  4. 4. Create a complete backup of the Apex One server configuration and database
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Apply the upgrade following Trend Micro's standard upgrade procedure for your deployment type
  7. 7. Verify the installation was successful and the version number matches the expected fixed release
  8. 8. Confirm the vulnerability is resolved through the product console or version check
Caveat Review Trend Micro release notes for any configuration or feature changes between your current version and the target fixed version before upgrading

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
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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