An issue related to case-sensitivity settings may result in unsuccessful Active Directory synchronization.

A known vulnerability (CVE-2018-1285) is found in Apache log4net 2.0.10 and earlier versions.

Active Directory user names containing a single quote character may cause the system to send email messages with the one-time report every minute.

An issue related to security headers causes the "Control traffic on isolated endpoints" setting to be unconfigurable.

A missing byte-order mark (BOM) in the CSV file exported from the User-Defined Suspicious Objects screen causes the system to display garbled text on the web console after importing the file.

A known vulnerability (CVE-2022-31629) is found in PHP 7.4.32 and earlier versions.

A Session Fixation vulnerability is found in Apex Central.

No logs display when users single sign-on to Apex One and try to perform a log search from the Agent Tree or view detection logs from the Dashboard.

When using the XCOPY or ROBOCOPY command in Microsoft Windows, the system does not block USB storage drives based on the Device Control settings.

When Data Loss Prevention (DLP) settings are configured in Security Agents to monitor sensitive data, the system may generate false-positive DLP alerts.

On the Apex Central web console, users may not be able to delete the Behavior Monitoring Approved Lists in Policy Settings.

When the "Automatic proxy setup" function is enabled in Windows network proxy settings, Apex One Security Agents may use an invalid proxy server for network connections and appear as "Offline" on the Apex One web console.

An issue in Apex One Security Agent may cause the File Reputation Service (FRS) to appear as "N/A" on the Agent Management screen.

When Data Loss Prevention (DLP) is enabled on Apex One Security Agent endpoints, HCL Notes (formerly IBM Notes and Lotus Notes) may become unresponsive.

An issue related to the digital signature checking process in Apex One Security Agent may cause continuous component downloads creating excessive network traffic and resulting in unsuccessful agent program updates.

The Web Reputation Service (WRS) does not function properly in Internet Explorer or Google Chrome web browser.

Sometimes, Apex One Security Agents may automatically start a program upgrade process.

A compatibility issue between the Trend Micro User Mode Hooking (UMH) component in Apex One Security Agent and the Refinitiv Workspace application may cause the Refinitiv Workspace application to not function properly.

An issue related to the forensic data process in Data Loss Prevention (DLP) may cause the Apex One server to become unresponsive and all Apex One Security Agents to appear as "Offline" on the web console.

This Critical Patch adds a new CEF key "TMCMdevicePlatform" to include the operating system information in all detection syslogs.

This Critical Patch fixes the SQL injection security issue.

This Critical Patch enhances the performance of historical investigation when multiple Apex One servers are connected to Apex Central.

This Critical Patch updates the related modules to prevent the username information from being exposed in the Uniform Resource Locator (URL).

This Critical Patch enables Apex Central to display Apex One (Mac) policies in Product Status View.

This Hotfix enables the Apex One Security Agent program to support Microsoft Windows 10 22H2.

This Hotfix enables the Apex One Security Agent program to support the maximum limit for the URL type in the Suspicious Object list. For more information, see "https://success.trendmicro.com/solution/000291262".

This Hotfix updates the Apex One Security Agent program to protect against the Link Following Local Privilege Escalation security issue.

This Hotfix updates the Anti-Spyware Engine (SSAPI) to version 6.2.1.4063 to resolve potential Local Privilege Escalation security issues.

This Hotfix updates the Apex One Security Agent program to protect against the Link Following Local Privilege Escalation security issue.

This Hotfix updates the Advanced Threat Scan Engine (ATSE) to version 22.580.1004 and enables Apex One Security Agent to scan and detect the Breach and Attack Simulation (BAS) Tools for the Predictive Machine Learning module and CVE exploit scanning.

This Hotfix updates the Behavior Monitoring Core Service module to version 2.98.1891 and the Behavior Monitoring Core Drive module to version 2.98.1890.

This Hotfix updates the Trend Micro xHandler module to version 1.200.1007.

This Hotfix updates the Apex One Security Agent program to resolve multiple Implicit Linking issues.

This Hotfix enables the Apex One (Mac) Security Agent program to support Chrome extension Manifest Version 3.

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.

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.