This Hotfix resolves the following issue(s):
In web access policy violation event notifications, the URL field may contain the complete URLs of malicious websites that users can click.
Solution
This Hotfix resolves this issue.
The system does not send a cookie that is not set to secure in HTTPS connections.
Solution
This Hotfix sets the cookie to secure to resolve this issue.
The system does not display the required pattern/engine properly on the Download screen due to unsuccessful configuration file merge.
Solution
This Hotfix resolves the issue.
This Hotfix resolves the following issue(s):
A Unicode character issue may prevent Apex One Security Agent from detecting and blocking domain user-defined suspicious objects (UDSO) properly.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
A process injection issue related to the Behavior Monitoring module may cause the Trend Micro Security Agent Monitor ("PccNTMon.exe") process to stop unexpectedly on Security Agent endpoints running Microsoft™ Windows™ 10 (32-bit).
Solution
This Hotfix updates the Behavior Monitoring Core Driver and Behavior Monitoring Core Service modules to version 2.98.1814 to resolve this issue.
When Data Protection is activated and Apex One Security Agent detects sensitive data during file transfers and displays a pop-up event notification, the network interface on the Security Agent endpoint may be disabled unexpectedly.
Solution
This Hotfix updates the Data Protection module to version 6.2.5146 to resolve this issue.
A deadlock issue related to the Trend Micro Unauthorized Change Prevention ("TMBMSRV.exe") service may cause the system to become unresponsive.
Solution
This Hotfix allows users to configure the Behavior Monitoring feature to resolve this issue.
Procedure
To update the setting and deploy the solution:
There are no issues for this Hotfix release.
The following enhancements are included in this Hotfix:
This Hotfix adds the event messages in debug logs for the EncryptDecryptUtility module.
The following enhancements are included in this Hotfix:
This Hotfix updates the Trend Micro Osprey module in Apex One Security Agent to version 5.1.1092 to protect against a potential Local Privilege Escalation security issue.
This Hotfix enhances the Digital Signature integrity checking process of the Apex One Security Agent program to resolve a Local Privilege Escalation security issue.
This Hotfix enables Apex One Security Agent to support the use of wildcard characters in the Scan Exclusion settings for the Sample Submission feature.
This Hotfix updates the icon for Trend Micro Apex One Security Agent on endpoints.
The Hotfix removes the version roll-back feature for Apex One Security Agent to prevent a potential security issue.
This Hotfix enables Apex One Security Agent to redeploy the Trend Micro Endpoint Basecamp service after moving Security Agents to another Apex One server.
This Hotfix enhances the Issuer Information Checking mechanism of the Apex One server program to improve product security.
The following enhancements are included in this Hotfix:
This Hotfix enables the Apex One (Mac) Security Agent program to support installation on endpoints using the Apple(R) M2 processor.
This Hotfix updates the signature of the Google Chrome profile file to the latest version.
Security Agent version: 14.0.11676
Security Agent restart: Required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
Security Agent Version: 3.5.6202
Security Agent Restart Requirement: Not required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
64-bit Security Agent Hotfix = 215MB
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.