This Hotfix resolves the following issue(s):
A potential Cross-Site Scripting (XSS) vulnerability is found in Apex Central.
Solution
This Hotfix updates the related modules to resolve the issue.
Users are unable to search for specific Security Agent endpoints in Apex Central.
Solution
This Hotfix updates the related modules to resolve the issue.
Single Sign-On (SSO) to the Apex One web console from the Apex Central web console may be unsuccessful.
Solution
This Hotfix updates the related modules to resolve the issue.
Widgets on the Dashboard may be exposed to potential Cross-Site Scripting (XSS) vulnerabilities.
Solution
This Hotfix updates the related components to protect against the vulnerabilities.
A key press issue on the Log On screen prevents users from accessing the web console.
Solution
This Hotfix resolves the issue.
The system may include garbled text in event notification email messages that contain Japanese characters.
Solution
This Hotfix resolves the issue.
Users are unable to view detailed Predictive Machine Learning log information from the Users/Endpoints screen.
Solution
This Hotfix resolves the issue.
This Hotfix resolves the following issue(s):
An issue related to the version change mechanism in Apex One Security Agent may prevent the system from upgrading the OpenSSL library to version 3.0.7.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
When the Trend Micro Unauthorized Change Prevention service ("TMBMSRV.exe") stops unexpectedly, Apex One Security Agent may not be able to update the Behavior Monitoring Detection Pattern properly.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
After disabling the POP3 email scanning feature, the Apex One NT Listener service ("TmListen.exe") is unable to perform some file operations.
Solution
This Hotfix updates the Apex One Security Agent program to resolve the issue.
An issue related to the certificate integrity checking for Azure Code Signing (ACS) in Apex One Security Agent may prevent the system from performing an agent update successfully and result in excessive network bandwidth usage due to multiple component update downloads.
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 updates the web console to include the "HTTPS/HTTP" channel option for Data Loss Prevention logs on the Log Query screen.
This Hotfix adds the following columns for Data Loss Prevention logs in log query results on the web console:
This Hotfix adds a new drop-down list option (5 minutes) for the Web Console Timeout setting on the web console.
The following enhancements are included in this Hotfix:
This Hotfix updates the Anti-Spyware Engine (SSAPI) to version 6.2.1.4065 to resolve a potential Privilege Escalation security issue.
This Hotfix updates the Virus Scan Engine (VSAPI) and the Advanced Threat Scan Engine (ATSE) to version 22.610.1016 to support well-known and high-volume malware sample scanning.
This Hotfix enhances detection log collection by updating the Data Protection module to version 6.2.5207 for the Data Loss Prevention (DLP) feature in Apex One Security Agent.
This Hotfix enhances the process for Security Agent installer generation in Apex One to improve product security.
The following enhancements are included in this Hotfix:
This Hotfix updates the Trend Micro company logo on the Security Agent console and installation screens.
This Hotfix updates the Apex One (Mac) Security Agent program to enhance performance.
Security Agent version: 14.0.12105
Security Agent restart: Required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
Security Agent Version: 3.5.6802
Security Agent Restart Requirement: Not required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
64-bit Security Agent Hotfix = 221MB
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.