This Hotfix resolves the following issue(s):
When the "Adjust for daylight saving time automatically" setting is enabled, the system displays the incorrect timestamp for the CEF key "rt" value in Pattern/Engine Update Status logs.
Solution
This Hotfix resolves this issue.
During daylight saving time, the timestamp in email notifications is incorrect by one hour.
Solution
This Hotfix resolves the issue.
Policy data processing errors in the Application Control module cause the system to set the policy status to "With issue".
Solution
This Hotfix updates the related files to resolve the issue.
The system does not display the "Block" action for user-defined IP address suspicious objects imported using OpenIOC.
Solution
This Hotfix resolves the display issue.
The policy with the name "nopolicy" prevents the system from displaying the policy list properly.
Solution
This Hotfix resolves the issue.
This Hotfix resolves the following issue(s):
Enabling Application Control may affect system performance on Security Agent endpoints.
Solution
This Hotfix updates the Application Control Agent program to resolve this issue.
During daylight saving time, the timestamp for Application Control Agent logs is incorrect by one hour.
Solution
This Hotfix updates the Application Control Agent program to resolve this issue.
During the VGSTUDIO MAX installation process, the Apex One Security Agent endpoint may become unresponsive.
Solution
This Hotfix updates the Program Inspection Engine to version 2.9.1048 to resolve this issue.
The Trend Micro Unauthorized Change Prevention ("TMBMSRV.exe") service may stop unexpectedly.
Solution
This Hotfix updates the Behavior Monitoring Core Service module to version 2.98.1912 to resolve this issue.
Apex One Security Agents may not send the correct Active Directory (AD) user information to the Apex One server.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
A server-agent communication issue may prevent agent updates or upgrades for Security Agents acting as Update Agents.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
When Data Loss Prevention (DLP) is enabled, Security Agents may not detect and block file upload through FTP.
Solution
This Hotfix updates the Data Protection module to version 6.2.5188 to resolve this issue.
There are no issues for this Hotfix release.
The following enhancements are included in this Hotfix:
This Hotfix updates the log query module to protect against Cross-Site Scripting (XSS) security issues.
This Hotfix enables Apex Central to display the policy name and version information on the Log Query screen for Apex One (Mac) Security Agents.
The following enhancements are included in this Hotfix:
This Hotfix updates the OpenSSL library in Apex One to version 3.0.7 and the cURL binary to version 7.86 to enhance product security.
This Hotfix enables Apex One to reset the Suspicious Object (SO) lists after users click Unsubscribe on the Suspicious Object List Settings screen in the Apex One web console.
This Hotfix enables Apex One Security Agent to use Azure Code Signing (ACS) for certificate integrity checking.
This Hotfix updates the Apex One server program to resolve a possible File Uploading Vulnerability security issue.
The following enhancements are included in this Hotfix:
This Hotfix enables Apex One (Mac) Security Agent to display the policy name and version on the "Component Versions" screen.
This Hotfix updates the copyright information to year 2023 on the About screen in Apex One (Mac).
Security Agent version: 14.0.11960
Security Agent restart: Required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
Security Agent Version: 3.5.6711
Security Agent Restart Requirement: Not required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
64-bit Security Agent Hotfix = 219MB
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.