This Hotfix resolves the following issue(s):
A potential Cross-Site Scripting (XSS) vulnerability is found in Apex Central.
Solution
This Hotifx updates the related modules to resolve the issue.
Potential Cross-Site Scripting (XSS) security issues are found in the Endpoint Encryption Plug-in in Apex Central.
Solution
This Hotifx updates the Endpoint Encryption Plug-in to resolve the issue.
An internal issue may cause component deployment to be unsuccessful.
Solution
This Hotfix resolves the issue.
This Hotfix resolves the following issue(s):
Duplicate Apex One device entries may appear on the Executive Dashboard in the Trend Vision One console.
Solution
This Hotfix updates the Apex One server program to resolve this issue.
Installing Trend Micro Security Agent on endpoints may prevent the system from performing a print operation.
Solution
This Hotfix updates the Trend Micro User-Mode Hook Event module in Apex One Security Agent to version 8.55.1257 to resolve this issue.
Apex One may not block USB storage devices based on the Device Control settings.
Solution
This Hotfix updates the Data Protection module to version 6.2.5255 to resolve this issue.
There are no issues for this Hotfix release.
The following enhancements are included in this Hotfix:
This Hotfix adds the API URL information on the Automation API Access Settings screen to enhance product integration.
This Hotifx enables managed Apex One servers to send server configuration information to Trend Vision One to enhance product integration. NOTE: This feature requires the installation of Apex One Service Pack 1 Patch 1 or above.
Enhance the data consistency and accuracy between Apex One as a Service and Trend Vision One Standard Endpoint Protection.
The following enhancements are included in this Hotfix:
This Hotfix enhances the component duplication function for the Security Agents act as Update Agents in Apex One.
This Hotfix updates the verification method to support certificate integrity checking for Azure Code Signing (ACS).
This Hotfix updates the OpenSSL library to version 3.0.9 and the cURL binary to version 8.1.2 in Apex One server and Security Agent programs to enhance product security.
This Hotfix adds a version check process in Apex One Security Agent for Trend Micro Endpoint Basecamp service installation to avoid installing an older version.
This Hotfix updates the Advanced Threat Scan Engine (ATSE) to version 23.570.1002 and enables ATSE in Apex One Security Agent to support on-demand memory scan to prevent process memory scan attacks.
This Hotfix enables Apex One Security Agent to support Advanced Malware Detection feature that uses machine learning to detect malware and spyware threats in portable executable files and applies the selected action.
The following enhancements are included in this Hotfix:
This Hotfix updates the associated JSON framework in Apex One (Mac) server to version 10.0 to enhance product security.
This Hotfix enables the system to clear policy settings associated with Apex One (Mac) Security Agents that are transferred to another Apex One (Mac) server.
This Hotfix updates the restricted group names for the Apex One (Mac) server.
Security Agent version: 14.0.12684
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.7254
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.