Saturday, January 4, 2025
HomeCVE/vulnerabilityTrend Micro Apex One Vulnerabilities Let Escalate Privilege

Trend Micro Apex One Vulnerabilities Let Escalate Privilege

Published on

SIEM as a Service

Trend Micro has addressed six high-severity vulnerabilities in its Apex One and Apex One as a Service product, which could allow attackers to escalate privileges on affected Windows systems.

These vulnerabilities were disclosed under the Common Vulnerabilities and Exposures (CVE) system and have been resolved in the latest builds released by Trend Micro.

The vulnerabilities could potentially allow local attackers to gain elevated privileges and execute malicious operations on compromised systems. Trend Micro strongly recommends all users update their installations to mitigate potential security risks.

- Advertisement - SIEM as a Service

Vulnerabilities Summary

CVE IDDescription
CVE-2024-52048LogServer Link Following Local Privilege Escalation
CVE-2024-52049LogServer Link Following Local Privilege Escalation (variant of CVE-2024-52048)
CVE-2024-52050LogServer Arbitrary File Creation Local Privilege Escalation
CVE-2024-55631Engine Link Following Local Privilege Escalation
CVE-2024-55632Security Agent Link Following Local Privilege Escalation
CVE-2024-55917Origin Validation Error Local Privilege Escalation

Affected Versions

ProductAffected VersionsPlatformLanguage
Apex OneVersions before Build 13140WindowsEnglish
Apex One as a ServiceVersions before 202412 (Agent Version: 14.0.14203)WindowsEnglish

Solution

To address these vulnerabilities, Trend Micro has released the following updates:

ProductUpdated VersionAvailability
Apex OneSP1 Build 13140Now Available
Apex One as a ServiceDecember 2024 MaintenanceNow Available

Customers can download these updates via the Trend Micro Download Center. Ensure all prerequisite service packs are applied before installation.

To mitigate the risks posed by these vulnerabilities, Trend Micro advises organizations to take immediate action.

First and foremost, ensure that the latest patches and updates are applied promptly to affected Apex One products, as the vulnerabilities require system updates to be addressed effectively.

Since exploiting these issues typically requires an attacker to have local access to the target machine, organizations should also restrict physical and remote access to critical systems.

Reviewing and updating perimeter security measures, such as access controls and remote access policies, is crucial to minimizing exposure.

Adopting robust cybersecurity best practices, including privileged access management, network segmentation, and proactive monitoring, can provide an additional layer of defense against similar exploitation attempts in the future.

Investigate Real-World Malicious Links, Malware & Phishing Attacks With ANY.RUN – Try for Free

Divya
Divya
Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Latest articles

LegionLoader Abusing Chrome Extensions To Deliver Infostealer Malware

LegionLoader, a C/C++ downloader malware, first seen in 2019, delivers payloads like malicious Chrome...

ASUS Critical Vulnerabilities Let Attackers Execute Arbitrary Commands

In a recent security advisory, ASUS has alerted users to critical vulnerabilities affecting several...

NTT Docomo Hit by DDoS Attack, Services Disrupted for 11 Hours

NTT Docomo, one of Japan’s leading telecommunications and IT service providers, experienced a massive...

Apple Agrees to $95M Settlement Over Siri Privacy Lawsuit

Apple Inc. has agreed to pay $95 million to settle a proposed class-action lawsuit...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

LegionLoader Abusing Chrome Extensions To Deliver Infostealer Malware

LegionLoader, a C/C++ downloader malware, first seen in 2019, delivers payloads like malicious Chrome...

ASUS Critical Vulnerabilities Let Attackers Execute Arbitrary Commands

In a recent security advisory, ASUS has alerted users to critical vulnerabilities affecting several...

NTT Docomo Hit by DDoS Attack, Services Disrupted for 11 Hours

NTT Docomo, one of Japan’s leading telecommunications and IT service providers, experienced a massive...