Vulnerabilities (CVE)

Filtered by vendor Trellix Subscribe
Filtered by product Agent
Total 6 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2024-0213 1 Trellix 1 Agent 2024-01-12 N/A 7.8 HIGH
A buffer overflow vulnerability in TA for Linux and TA for MacOS prior to 5.8.1 allows a local user to gain elevated permissions, or cause a Denial of Service (DoS), through exploiting a memory corruption issue in the TA service, which runs as root. This may also result in the disabling of event reporting to ePO, caused by failure to validate input from the file correctly.
CVE-2023-1388 1 Trellix 1 Agent 2023-12-10 N/A 8.1 HIGH
A heap-based overflow vulnerability in TA prior to version 5.7.9 allows a remote user to alter the page heap in the macmnsvc process memory block, resulting in the service becoming unavailable.
CVE-2023-0975 2 Microsoft, Trellix 2 Windows, Agent 2023-12-10 N/A 7.8 HIGH
A vulnerability exists in Trellix Agent for Windows version 5.7.8 and earlier, that allows local users, during install/upgrade workflow, to replace one of the Agent’s executables before it can be executed. This allows the user to elevate their permissions.
CVE-2023-0977 3 Linux, Microsoft, Trellix 3 Linux Kernel, Windows, Agent 2023-12-10 N/A 6.5 MEDIUM
A heap-based overflow vulnerability in Trellix Agent (Windows and Linux) version 5.7.8 and earlier, allows a remote user to alter the page heap in the macmnsvc process memory block resulting in the service becoming unavailable.
CVE-2023-0976 2 Apple, Trellix 2 Macos, Agent 2023-12-10 N/A 7.8 HIGH
A command Injection Vulnerability in TA for mac-OS prior to version 5.7.9 allows local users to place an arbitrary file into the /Library/Trellix/Agent/bin/ folder. The malicious file is executed by running the TA deployment feature located in the System Tree.
CVE-2022-3859 1 Trellix 1 Agent 2023-12-10 N/A 6.7 MEDIUM
An uncontrolled search path vulnerability exists in Trellix Agent (TA) for Windows in versions prior to 5.7.8. This allows an attacker with admin access, which is required to place the DLL in the restricted Windows System folder, to elevate their privileges to System by placing a malicious DLL there.