dbcve.org
Apex OneApplication · Trendmicro

CVE-2024-52050

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
A LogServer arbitrary file creation 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

A LogServer arbitrary file creation vulnerability in Trend Micro Apex One allows a local attacker with low-privileged code execution to create files in arbitrary locations on the filesystem, potentially overwriting system files or placing malicious executables in privileged paths to achieve privilege escalation to SYSTEM level.

MitigationApply the vendor-supplied patch for CVE-2024-52050 when available; until then, restrict write access to LogServer directories and monitor for suspicious file creation activity by low-privileged accounts.

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. Identify Apex One installation path
    Look for the Apex One installation directory, typically at C:\Program Files\Trend Micro\Apex One or C:\Program Files (x86)\Trend Micro\Apex One. Check registry key HKLM\SOFTWARE\TrendMicro\Apex One\InstallPath for the exact path.
    Affected if Apex One is installed in the standard location or registry key exists
  2. Determine installed Apex One version
    Check the version by opening the file properties of the main executable (e.g., ossec.exe or TmCCfg.exe in the Apex One directory), or query the registry at HKLM\SOFTWARE\TrendMicro\Apex One\CurrentVersion for the version string.
    Affected if Version is lower than 14.0.14203 or 2019.13140 (for older release branches)
  3. Locate LogServer component and directories
    Navigate to the Apex One installation directory and locate the LogServer subfolder (commonly at path\LogServer or path\PCCNT\MON\LogServer). This component handles logging for the security agent.
    Affected if LogServer directory exists within the Apex One installation folder
  4. Verify LogServer service presence
    Open Services (services.msc) and look for a service related to LogServer, or check running processes for LogServer.exe or similar executable names under the Trend Micro process tree.
    Affected if LogServer service or executable is present and running
  5. Check write permissions on LogServer directories
    Right-click the LogServer folder, go to Properties > Security, and examine which users or groups have Write or Create Files permissions. Use icacls.exe from command line (e.g., icacls "path\LogServer") to list effective permissions.
    Affected if Low-privileged users or groups (non-admin) have Write or Create permissions on LogServer directories

If Apex One is installed with a version below 14.0.14203 (or below 2019.13140 for older branches) AND the LogServer component exists with weak permissions allowing low-privileged users to create files, the environment is vulnerable to CVE-2024-52050.

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-supplied patch for CVE-2024-52050 when available; until then, restrict write access to LogServer directories and monitor for suspicious file creation activity by low-privileged accounts.

Recommended fix High confidence

Apex One version 14.0.14203 or later; Apex One version 2019.13140 or later

  1. Verify current Apex One version by checking the product console or installed binaries
  2. Review release notes at success.trendmicro.com for version 14.0.14203 (or later) and version 2019.13140 (or later) to confirm included security fixes
  3. Create a full backup of the Apex One database and configuration settings
  4. Download the appropriate patched installer from the Trend Micro Customer Licensing Portal or official download center
  5. Schedule a maintenance window and notify affected users
  6. Stop the Apex One services on the server
  7. Run the upgrade installer, selecting 'Upgrade' option
  8. Verify successful completion and check that services start correctly
Caveat Review release notes for any configuration changes or compatibility considerations 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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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