dbcve.org
Apex OneApplication · Trendmicro

CVE-2024-52049

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 link following vulnerability in Trend Micro Apex One could allow a local attacker to escalate privileges on affected installations. This vulnerability is similar to, but not identical to CVE-2024-52048. 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 symlink-based (link following) local privilege escalation vulnerability in the LogServer component of Trend Micro Apex One. An attacker with low-privileged code execution can exploit improper symlink handling to gain elevated privileges on the affected system.

MitigationApply the vendor-supplied patch for CVE-2024-52049 to the Apex One installation. As this requires low-privileged code execution first, ensure strict least-privilege policies and monitor for anomalous local privilege escalation attempts.

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 installed Apex One version
    Locate the Apex One installation directory (typically in Program Files) and check for version information in the main executable, registry, or version file. Common locations include the root installation folder or HKLM\SOFTWARE\TrendMicro\Apex One in the registry.
    Affected if The installed version is below 14.0.14203 or below 2019.13140 (the version number format depends on the release branch)
  2. Confirm LogServer component presence
    Locate the LogServer component within the Apex One installation directory. This is typically found in a subfolder named 'LogServer' or similar within the main product directory.
    Affected if The LogServer component is present and running as a service on the system
  3. Verify service configuration for LogServer
    Check the LogServer Windows service configuration to determine the account it runs under. This can be done via Services.msc or the sc queryex command.
    Affected if The LogServer service runs under a high-privilege account (such as SYSTEM or a domain admin) and the version is vulnerable
  4. Check for recent file system activity in LogServer directory
    Review the file system permissions and recent modification timestamps in the LogServer directory. Look for any unexpected symlinks or unusual file creations.
    Affected if World-writable directories exist within the LogServer component path that could allow symlink manipulation

The environment is affected if Trend Micro Apex One is installed with a version lower than 14.0.14203 or lower than 2019.13140 and the LogServer component is present on the system.

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-52049 to the Apex One installation. As this requires low-privileged code execution first, ensure strict least-privilege policies and monitor for anomalous local privilege escalation attempts.

Recommended fix High confidence

Apex One 14.0.14203 (14.x branch) or Apex One 2019 build 13140 (2019 branch)

  1. Identify the currently installed Apex One version by checking the product About or version information
  2. Determine which branch of Apex One is in use (14.x or 2019) based on the current version
  3. Download the corresponding fixed release: Apex One 14.0.14203 or later for the 14.x branch, or Apex One 2019 build 13140 or later for the 2019 branch
  4. Review the upgrade prerequisites and ensure compatibility with the current operating system and any integrated products
  5. Create a full backup of the Apex One configuration and database before proceeding
  6. Execute the upgrade installer with administrative privileges
  7. Verify the upgrade completed successfully by checking the new version number
  8. Confirm the LogServer service is running properly post-upgrade
Caveat Standard upgrade considerations apply - review release notes for any configuration or feature changes; test in staging environment before production deployment

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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