This Hotfix resolves the following issue(s):
A potential open redirect vulnerability is found in the Apex Central widget module.
Solution
This Hotfix updates the module to protect against the vulnerability.
A potential cross-site scripting (XSS) vulnerability is found in the Apex Central widget module.
Solution
This Hotfix updates the module to protect against the vulnerability.
An issue related to product profile merge may prevent the system from displaying the correct product information.
Solution
This Hotfix resolves the issue.
Some cookies do not include the Secure attribute.
Solution
This Hotfix resolves the issue.
An internal issue causes the system to display entries for Security Agent endpoints that do not exist on the Policies screen.
Solution
This Hotfix resolves the issue.
An issue related to suspicious object synchronization with Trend Vision One may cause the system to generate duplicate entries in the tb_blacklistrestjournal table in the Apex Central database.
Solution
This Hotfix updates the related module to resolve the issue.
This Hotfix resolves the following issue(s):
Trend Micro Apex One may not provide the correct virus and threat protection status in Windows Security.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
After installing the Apex One Security Agent on an endpoint, the Security Agent may use an invalid proxy server for network connections and appear as "Offline" in the Apex One web console.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
There are no issues for this Hotfix release.
The following enhancements are included in this Hotfix:
This Hotfix increases the maximum number of characters from 32 to 64 for the "User name" field on the Active Directory screen.
This Hotfix adds additional keyword dictionary to prevent false-positive detections for social security number (SSN) by Data Loss Prevention (DLP).
This Hotfix updates the user name display in audit logs for CEMI (CSV Excel Macro Injection).
This Hotfix enables the Apex Central web console to display up to 50 entries for user account search on the Assign Rule screen for Application Control policy settings.
The following enhancements are included in this Hotfix:
This Hotfix updates the 7-Zip module in Apex One to version 23.01 to enhance product security.
This Hotfix updates the "IPXfer.exe" server tool in Apex One to enhance product security.
This Hotfix updates the Apex One Security Agent program to protect against the Exposed Dangerous Function Local Privilege Escalation Vulnerability.
This Hotfix enables the telemetry monitoring mechanism in Apex One to automatically generate and send logs for Apex One Security Agent updates.
This Hotfix updates the Data Protection module to version 6.2.5268 and enables the Data Loss Prevention (DLP) module in Apex One Security Agent to monitor file activities from Zoho Web Mail on endpoints.
This Hotfix updates the Trend Micro Apex One Client Plug-in Service Manager module to protect against the Origin Validation Error Local Privilege Escalation Vulnerability.
The following enhancements are included in this Hotfix:
This Hotfix supports Apex One (Mac) Security Agent installation on endpoints running macOS 14 (Sonoma).
This Hotfix removes support for macOS 10.14 (Mojave) for Trend Micro Apex One (Mac) after November 2023.
Security Agent version: 14.0.12793
Security Agent restart: Yes
Security Agent OS reboot: Not required for Security Agents are running build versions later than 10000.
Estimated size of network traffic (in terms of bandwidth) required for deployment:
Security Agent Version: 3.5.7456
Security Agent Restart Requirement: Not required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
64-bit Security Agent Hotfix = 241MB
Additional Requirements: Enable web browser extension (https://success.trendmicro.com/solution/000273346)
No post-installation steps are required.
NOTE: Trend Micro recommends that you update your scan engine and virus pattern files immediately after installing the product.
There are no known issues for this Hotfix release.
Known issues in this release:
Security Agent consoles running build 13.95 display an incorrect policy name. To resolve this issue, upgrade the Security Agent to 14.0. After the Security Agent contacts the server, the policy name displays correctly.
Off-premises and Security Agents in Independent mode cannot update the Certified Safe Software Pattern from external update sources.
Coexist mode Security Agents on endpoints with Windows Defender may experience installation issues or be unable to upload data to the Apex One server due to a file locking issue. To resolve this issue, add Endpoint Sensor (ESEServiceShell.exe and ESClient.exe) in the exclusions list of Windows Defender to prevent the locking issue.
After copying a file to a remote server using a relative path as the source, Apex One is unable to translate the relative path into the full system directory.
The quality of RCA analysis chain image files is reduced when viewing the files using Windows 10 Photo Viewer.
When attempting to start a Historical Investigation from the Attack Discovery Detections widget that includes Registry value name or Registry value data criteria, the Historical Investigation displays an error message if the length of the Registry value name exceeds 260 characters or the Registry value data exceeds 64 characters.
After updating the Attack Discovery Pattern file (tmesadp.ptn) on Security Agents, a database schema error may occur that causes the Endpoint Sensor feature to continuously report the same detections to the server during each synchronization. This causes duplicate records to display on the Apex Central server.
Root Cause Analysis email attachment results may also include temporary files created when the user saved the file.
The number of matched endpoints that display on a Root Cause Analysis chain may appear to be greater than the total if the Security Agent on an endpoint was uninstalled or no longer reports to the same managing server.
The Endpoint Sensor service may have high memory usage.
The Endpoint Sensor may have high peak CPU usage occasionally.
Endpoint Sensor has CPU peak during Windows Update phase.
The user or account name in ADE detection may be empty.
The EC module may stop responding while handling NULL data which may cause the ESEService and ADE functionality to behave abnormally.
In rare conditions, ESEService stops responding while unloading.
Known issues in this release:
After enabling the Scan Time Machine option for Manual Scan and Scheduled Scan, Apex One (Mac) cannot perform any actions (clean, quarantine, or delete) on detected malware threats due to a permission limitation in Mac OS. Configured scan actions are displayed as unsuccessful in the product logs.
When performing a historical investigation on Apex One (Mac) endpoints, the system replaces a slash (/) with a colon (:) in file names, preventing users from searching for file names that contain backslashes in investigation results.
To resolve this issue, use a colon (:) to search for the files.