dbcve.org
Apex OneApplication · Trendmicro

CVE-2024-58105

HIGH · 7.8 CVSS v3.1 Published 2025-03-25
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 vulnerability in the Trend Micro Apex One Security Agent Plug-in User Interface Manager could allow a local attacker to bypass existing security and execute arbitrary code on affected installations. This CVE address an addtional bypass not covered in CVE-2024-58104. 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 vulnerability in the Trend Micro Apex One Security Agent Plug-in User Interface Manager allows a local attacker with low-privileged code execution capability to bypass existing security controls and execute arbitrary code on affected installations. This CVE represents an additional security bypass not addressed in the related CVE-2024-58104.

MitigationApply the vendor-supplied security patch or update to Trend Micro Apex One Security Agent to address the UI Manager component vulnerability. Organizations should also maintain least-privilege principles and monitor for unauthorized 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. Verify Trend Micro Apex One is installed
    Locate the Apex One installation directory or check system for Apex One software components
    Affected if Apex One Security Agent is not present on the system
  2. Identify the installed Apex One version
    Use system inventory tools, registry entries, or the product's built-in version information to determine the exact installed version number
    Affected if The version cannot be determined or the product is not found
  3. Compare version against affected ranges
    Compare your installed version to the vulnerable thresholds: versions below 14.0.14203 and versions below 2019.13140 are affected
    Affected if Installed version is less than 14.0.14203 OR less than 2019.13140
  4. Check for the UI Manager component
    Verify the presence of the Plug-in User Interface Manager component within the Apex One Security Agent installation
    Affected if The UI Manager component exists on a version that falls within the affected version ranges

A system is affected if Trend Micro Apex One Security Agent is installed with a version number below 14.0.14203 or below 2019.13140, and the UI Manager component is present.

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 security patch or update to Trend Micro Apex One Security Agent to address the UI Manager component vulnerability. Organizations should also maintain least-privilege principles and monitor for unauthorized local privilege escalation attempts.

Recommended fix Moderate confidence

Apex One 14.0.14203 or later / Apex One 2019.13140 or later

  1. Verify current Apex One Security Agent version by checking the product console or installed software list
  2. Download the latest Apex One patch from the Trend Micro Download Center or your licensed portal
  3. For Apex One (14.x): Upgrade to version 14.0.14203 or later
  4. For Apex One (2019): Upgrade to version 2019.13140 or later
  5. Apply the update through the Apex One server management console
  6. Verify the update was successful by checking the agent version post-installation
  7. Restart the Apex One services if required by the patch
Caveat Review release notes for any configuration or compatibility changes before upgrading production systems

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 / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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