ICS-Advisories

Risk Evaluation

ABB is aware of public reports of vulnerabilities in third-party components (PHP and NTFS-3G) included in the product versions listed as affected in the advisory. An attacker who successfully exploited these vulnerabilities may insert and run arbitrary code on affected products. No active exploitations of the vulnerabilities have been reported to ABB by the time of writing this document. ABB will inform affected customers if this changes.

Zusammenfassung der Gegenmaßnahmen

For the products and version numbers listed below, please apply the relevant software patches according to the instructions provided by your ABB contact. - IPEC iSM Local Server: Debian 11 (Bullseye) - IPEC iSM Local Server: Debian 12 (Bookworm) - IPEC iSM Local Server: Debian 13 (Trixie) If further support is required to install the patches, please contact IPEC Sales (ipec.sales@gb.abb.com). Installation support may be chargeable where not covered by your existing warranty, maintenance or support agreement. ABB recommends that customers apply the update as soon as possible.

Risk Evaluation

ABB is aware of publicly reported information concerning recently disclosed PHP vulnerabilities that impact the product versions listed as affected in the advisory. An attacker who successfully exploited this vulnerability may insert and run arbitrary code on affected products.

Zusammenfassung der Gegenmaßnahmen

The problem is corrected in the following software release packages published for products: - Netcon 200 (GWDD-A03): Software release A103.03.020 published Nov-2-2026 ABB recommends that customers apply the update at earliest convenience. The process to install updates and identify the installed product version is described in the user manual and release note document attached to installation package.

Risk Evaluation

An update is available that resolves a publicly reported vulnerability in the product versions listed as affected in the advisory. An attacker who successfully exploited this vulnerability could cause the product to stop, disclose process memory or insert and run arbitrary code.

Zusammenfassung der Gegenmaßnahmen

The problem is corrected by updating the Node.js runtime used by the product versions listed as affected. A new ABM release containing the patched runtime is not yet available; until then, the runtime must be updated manually: - Node.js 24.x (ABM 1.2, 1.2.1): Update to Node.js 24.22.1 or later within the 24.x line. This version has been successfully tested with the ABM standard. ABB recommends that customers apply the update at earliest convenience. Major-version changes require compatibility testing before a production restart. Where ASP.NET Core / .NET components are deployed together with ABM, ABB additionally recommends installing the vendor-patched .NET releases.

Risk Evaluation

ABB is aware of publicly reported information concerning recently disclosed PHP vulnerabilities that impact the product versions listed as affected in the advisory. An attacker who successfully exploited this vulnerability may insert and run arbitrary code on affected products. As part of ABB product lifecycle policy, once a product transitions to obsolete state, we discontinue maintenance, security patches, and technical support to focus on current and future technologies. While the product will continue to function, we strongly recommend implementing the mitigations de-fined in this document to reduce security risks.

Zusammenfassung der Gegenmaßnahmen

Mitigating factors describe conditions and circumstances that make an attack that exploits vulnerability difficult or less likely to succeed. - Obtain a private cellular Access Point (private APN). A dedicated private APN and the corresponding SIM card subscriptions can be obtained from your cellular service provider. This service does not expose traffic between remote sites and the main site to the Internet. Instead, communication is carried over the cellular operator’s private wide area network (WAN). Therefore, the ARM600 does not require any inbound ports to be exposed to the Internet. - Avoid exposing any system component directly to the Internet. If the ARM600 must be exposed to the Internet, only the VPN port should be accessible from the Internet. Patrol management connections can be configured to use a VPN tunnel, and remote administration can be performed using an PC OpenVPN client or another VPN solution that provides mutual authentication. - Establish Demilitarized Zone (DMZ) architecture, where the ARM600 server is deployed in the DMZ to terminate VPN connections from remote sites. The DMZ must be segregated from other networks by a firewall. - Configure the device firewall according to the allowlisting principle (i.e., explicitly allow only the required ports and protocols and block all other traffic). - Change the default user credentials of the ARM600 and Arctic wireless gateways, and use strong, non-guessable passwords that include special characters. Do not reuse passwords within the system.

Risk Evaluation

- General statement ABB became aware of vulnerabilities in ASPECT versions listed as affected in the advisory. The earliest report dates to Oct 2026. An attacker who successfully exploits these vulnerabilities may insert and run arbitrary code on affected products. ABB is currently investigating this vulnerability to provide adequate protection to customers. ASPECT is an on-premises Building Management System (BMS) that provides an additional option to be remotely accessible. - Statement on newly reported vulnerabilities ASPECT devices are not intended to be internet-facing. A product advisory issued in June 2023 informed customers regarding this fact. An attacker who successfully exploits these vulnerabilities could potentially gain unauthorized access and potentially compromise the system's - and log-file-confidentiality, integrity and availability. ABB requires, as noted in previous security advisories and user documentation, that ASPECT should not be exposed to the Internet or any other unsecured network. Note: To exploit ASPECT, an attacker would need a misconfigured system. ABB strongly advises customers and system integrators to follow the instructions documented in: FBXi, CBXi and ASPECT® SOLUTIONS, which can be downloaded from the ABB library.

Zusammenfassung der Gegenmaßnahmen

Please immediately do the following actions on any released SW version of ASPECT: - Stop and disconnect any ASPECT products that are exposed directly to the Internet, either via a direct ISP connection or via NAT port forwarding - Ensure that physical controls are in place, so no unauthorized personnel can access your devices, components, peripheral equipment, and networks - Ensure log-files, downloaded from the equipment is protected against unauthorized access - Ensure that all ASPECT products are upgraded to the latest firmware version. Please find the latest version of ASPECT firmware on the respective product homepage - When remote access is required, only use secure methods. If a Virtual Private Network (VPN) is used, ensure that the chosen VPN is secure i.e. updated to the most current version available and configured for secure access

Risk Evaluation

ABB is aware of publicly reported vulnerabilities in the product listed as affected in the advisory. Updates to the affected component that fixed the vulnerabilities are available. An attacker who successfully exploited this vulnerability could remotely execute code on the server run-ning Dokuwiki. No active exploitations of the vulnerabilities have been reported by the time of writing this document

Zusammenfassung der Gegenmaßnahmen

The vulnerabilities are not tight to any specific MES version but solely depend on the delivery including Dokuwiki, which relies on affected PHP versions. The affected PHP versions are listed in CERT-EU - Critical Vulnerabilities in PHP Reference section. The problem is corrected in the following product versions: • PHP 8.5.12 • PHP 8.4.27 • PHP 8.3.36 • PHP 8.2.35 ABB recommends that customers apply the updates immediately. The updates are applied by updating the PHP packages in operating system of the servers that run Dokuwiki. PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix two critical vulnerabilities that can allow unauthenticated remote code execution. All PHP users are strongly encouraged to update immediately. PHP is installed on the web server / operating system, so upgrading PHP is a server administration task. It needs to be checked which PHP packages are installed on the system, and upgrade them (depending on the OS, with either ‘dnf’ or ‘yum’). ABB recommends that only PHP packages are updated, not the whole Dokuwiki installation.

Risk Evaluation

ABB identified a critical vulnerability present in ABB Ability Edgenius versions 3.2.3.0 and below. We have not received any reports of this vulnerability being exploited. This issue may allow unauthorized manipulation of the edge authentication database if successfully exploited. ABB has developed and released a corrective update that resolves this vulnerability and enhances the security posture of the affected system.

Zusammenfassung der Gegenmaßnahmen

Workarounds are specific measures that a user can take to help block an attack, for example, temporarily disabling the vulnerable feature may remove exposure with well-known impact on functionality. For brownfield customers, ABB provides a Kubernetes network policy that restricts access to Edge Authentication Database (AuthDB) to the authorized services required for normal operation of an already deployed and configured system. For implementation details, refer to Technical Description-ABB Ability Edgenius Missing Authentication in Edgenius AuthDB.docx (7PAA025722) listed in the reference section, distributed separately.

Risk Evaluation

An update is available that resolves a privately reported vulnerability to the product versions listed as affected in the advisory. An attacker who successfully exploited this vulnerability could cause the node running the product to stop or to become inaccessible.

Zusammenfassung der Gegenmaßnahmen

Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. Refer to section General security recommendations for further advice on how to keep your system secure. For the reported issue there are no known mitigating factors.

Risk Evaluation

A local attacker who successfully exploited this vulnerability could gain elevated privileges by Path Traversal, arbitrarily reading files of system, to cause confidentiality impact of system files.

Zusammenfassung der Gegenmaßnahmen

Mint Workbench I 5876 and the versions before, are impacted, customers who use these products, should: - Disable Service MWI http when it is not in active use. - Restrict physical machine access to authorized personnel only. - Avoid storing sensitive or confidential data on any hosts running service MWI http. - Enable User Account Control (UAC) to block unauthorized privilege escalation attempts. These actions above are the only measures available. No further patch will be released because this product reaches end-of-life globally (out of China) by the end of 2026 and in China by the end of 2027. To exploit the vulnerability the attacker needs to have local access to the machine beforehand and have file write access in the path. Please also refer to section “General security recommendations” for further advise on how to keep your system secure.

Risk Evaluation

ABB is aware of vulnerabilities in the products versions listed as affected in the advisory. Automation Builder could execute arbitrary code by crafting the project file or project archive file.

Zusammenfassung der Gegenmaßnahmen

The problem is corrected in the following product version: - Automation Builder 2.9.1 ABB recommends that customers apply the update at earliest convenience. Automation Builder 2.9.1 is available for download from the related download site.

Risk Evaluation

An update is available that resolves publicly reported vulnerability in the products versions listed as affected in the advisory. An attacker who successfully exploited these vulnerabilities could cause a denial-of-service (DoS).

Zusammenfassung der Gegenmaßnahmen

The problem is corrected in the following product version: - AC500 V3 firmware version 3.9.1 ABB recommends that customers apply the update at earliest convenience. This firmware version is released for all AC500 V3 PLC types and integrated into Automation Builder 2.9.1. Automation Builder 2.9.1 is available for download from the related download site. https://www.abb.com/global/en/areas/motion/digital-tools/automation-builder/software-download

Risk Evaluation

ABB is aware of a privately reported vulnerability affecting the PCM600 project import functionality. An update is available that resolves this vulnerability in the affected product versions. A specially crafted PCM600 project archive may exploit insufficient validation of archive entry paths during project import. Successful exploitation could allow an attacker to create or overwrite files outside the intended extraction directory using the permissions of the importing user.

Zusammenfassung der Gegenmaßnahmen

The problem is corrected in the following product version: - ABB Protection and Control IED Manager (PCM600) version 2.14 Hotfix 20260923. This fixed version is available through the ABB Update Manager and ABB website: PCM600 | ABB ABB recommends that customers upgrade to the available hotfix at the earliest opportunity. Until the update can be applied, customers should follow the mitigation measures described in this advisory.

Risk Evaluation

ABB is aware of a reported vulnerability in ABB Protection and Control IED Manager (PCM600). A local authenticated user belonging to the PCM600 user group may be able to modify the configuration of a Windows service running with SYSTEM privileges. Successful exploitation could allow an attacker to execute arbitrary commands with elevated privileges on the affected workstation. Note: This document references the ABBPCMSchedulerService_v214 component as implemented in PCM600 version 2.14. However, the described issue is not version-specific and applies equally to the corresponding component in other supported versions of PCM600.

Zusammenfassung der Gegenmaßnahmen

ABB recommends the following workaround. Although this workaround does not correct the underlying vulnerability, it reduces the risk of privilege escalation. Configure the appropriate ABBPCMSchedulerService instance to run using the same Windows account that is used to operate PCM600. - Open Services.msc. - Locate the ABBPCMSchedulerService corresponding to the installed PCM600 version. - Open Properties and select the Log On tab. - The service should be configured to log on with the same Windows user account that is used for the PCM600 application. - Ensure that this account has the required "Log on as a service" privilege. When authentication is enabled for the IED, the Scheduler tool must be used with the same Windows account configured as the Scheduler Service logon account. For installations using IED security certificates, the PCM600 setting Always trust IED security certificates must be enabled only when PCM600-to-IED communication takes place in a secure and trusted environment. Impact of Workaround -Scheduler functionality will operate using the privileges of the configured Windows user account rather than SYSTEM privileges. - Users may need to be granted the "Log on as a service" Windows user right. - In environments using IED security certificates, enabling Always trust IED security certificates may reduce certificate validation protections and should only be used in secure and trusted environments. - Administrative effort may be required to maintain consistent user accounts between PCM600 and the Scheduler Service.

Risk Evaluation

ABB is aware of a vulnerability in the product versions listed as affected in the advisory. An update is available that resolves the reported vulnerability in the product versions under maintenance. An attacker who successfully exploited this vulnerability could cause the product to stop or make the product inaccessible.

Zusammenfassung der Gegenmaßnahmen

Refer to section “General security recommendations” for further advice on how to keep your system secure, as well checking the section “Workarounds”.

Risk Evaluation

ABB is aware of public reports of a vulnerability in the product listed as affected in the advisory. An update has been deployed to the cloud system that resolves a publicly reported vulnerability in the product versions listed above. An attacker who successfully exploited this vulnerability could take remote control of the product. The vulnerability has been identified in the keycloak authentication component which is integrated into dynovaPRO™. The vulnerability exists in the 'Forgot Password' functionality and allows unauthenticated attackers to bypass authentication and hijack user accounts. Users who have received a password reset mail before the mentioned date, without having requested it, are thereby potentially attacked by exploiting this vulnerability. ABB investigated potentially malicious user reset activities and blocked those user access immediately to reduce the exploitation risk. The credentials of those users have been deleted after the software fix was deployed and the users were informed that they must reset their password to gain access to dynovaPRO™ again.

Zusammenfassung der Gegenmaßnahmen

The following conditions reduce the risk of exploitation of this vulnerability: - Limited Attack Surface: The vulnerability is specific to the password reset functionality. Other authentication methods are not affected. - Email Notifications: Legitimate users receive email notifications during password reset attempts, which may alert them to unauthorized access attempts. Refer to section “General security recommendations” for further advise on how to keep your system secure.

Risk Evaluation

An update is available that resolves a publicly reported vulnerability in the product versions listed as affected in the advisory. An attacker who successfully exploited these vulnerabilities could - Allow arbitrary files to be deleted with system privileges (CVE-2026-81572), - Read potentially sensitive configuration data and overwrite selected values in Server.ini (CVE-2026-81573) - Crash CodeMeter and disclose sensitive information such as process memory and stack canar-ies (CVE-2026-81574) - Crash CodeMeter (CVE-2026-81575), or - Read potentially sensitive license information (CVE-2026-81576)

Zusammenfassung der Gegenmaßnahmen

For CVE-2026-81573, CVE-2026-81574, CVE-2026-81575, and CVE-2026-81576: If you enabled the network server functionality at some point but no longer need it, disable it: - Open the Registry Editor and navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ WIBUSYSTEMS\CodeMeter\Server\CurrentVersion\, then change the value of IsNetworkServerfrom 1 to 0. - Restart CodeMeter.

Risk Evaluation

ABB is aware of publicly disclosed security vulnerabilities affecting the WIBU-Systems CodeMeter Runtime for Windows, identified as CVE-2026-81572, CVE-2026-81573, CVE-2026-81574, CVE-2026-81575 and CVE-2026-81576. The CodeMeter Runtime component is used within affected ABB zenon Software Platform installations for software licensing and license server functionality. Successful exploitation of the reported vulnerabilities could enable local privilege escalation on Windows systems and impact systems configured as CodeMeter license servers, potentially leading to unauthorized access, service disruption, or loss of system integrity. Refer to the WIBU-Systems advisory for detailed technical information on each vulnerability. Please see the References section for the WIBU-Systems security advisory.

Zusammenfassung der Gegenmaßnahmen

ABB recommends the following mitigation measures: - Update the WIBU-Systems CodeMeter Runtime to version 8.41a or later. - The latest CodeMeter Runtime software is available from the WIBU-Systems download page: User Software - Wibu-Systems, please see the References section for the corresponding link. - Where upgrading is not feasible, ABB recommends that asset owners perform a risk assessment and implement compensating controls such as network isolation, access restrictions, and enhanced monitoring of affected systems. ABB recommends that customers apply the update at earliest convenience. The vulnerabilities associated with CVE-2026-81573, CVE-2026-81574, CVE-2026-81575 and CVE-2026-81576 are exploitable only when the WIBU-Systems CodeMeter Runtime is configured as a network server, which is not the de-fault configuration. The CVE-2026-81572 vulnerability requires local access to the affected Windows system and execution by a low-privileged user. Consequently, systems with restricted local access, proper privilege management, and limited network exposure are less likely to be successfully compromised. Refer to section “General security recommendations” for further advise on how to keep your system secure.

Risk Evaluation

An update is available that resolves publicly reported vulnerabilities in the product versions listed as affected in the advisory. An attacker who successfully exploited these vulnerabilities could - allow arbitrary files to be deleted with system privileges (CVE-2026-81572), - read potentially sensitive configuration data and overwrite selected values in Server.ini (CVE-2026-81573), - crash CodeMeter and disclose sensitive information such as process memory and stack canaries (CVE-2026-81574), - crash CodeMeter (CVE-2026-81575), or - read potentially sensitive license information (CVE-2026-81576)

Zusammenfassung der Gegenmaßnahmen

For CVE-2026-81572 the exposure can be limited by auditing the list of local users and removing any unnecessary accounts. For CVE-2026-81573, CVE-2026-81574, CVE-2026-81575, and CVE-2026-81576: If you enabled the network server functionality at some point but no longer need it, disable it: - Open the Registry Editor and navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ WIBUSYSTEMS\CodeMeter\Server\CurrentVersion\, then change the value of IsNetworkServerfrom 1 to 0. - Restart CodeMeter.

Risk Evaluation

ABB is aware of publicly reported vulnerabilities affecting MongoDB 4.2, which is bundled within the IIoT Services of the affected product versions. MongoDB 4.2 has reached end-of-life and contains multiple known security vulnerabilities. An attacker who successfully exploits these vulnerabilities could potentially access sensitive information, cause denial of service, or disrupt system availability.

Zusammenfassung der Gegenmaßnahmen

ABB recommends the following mitigation measures: - Replace bundled MongoDB with a supported version if IIoT services are required: - Where IIoT functionality is required, the bundled MongoDB instance can be replaced with a supported and patched version through manual configuration. - The following zenon online help section explains the process of installing and using your own MongoDB database: zenHelpViewer - Uninstall IIoT Services wherever it’s not required: - If IIoT Services are not required, they can be removed using the Control panel uninstaller. This eliminates the dependency on MongoDB without affecting other zenon components. Refer to section “General security recommendations” for further advise on how to keep your system secure.

Risk Evaluation

ABB is aware of publicly reported vulnerabilities affecting MongoDB 4.2, which is bundled within the IIoT Services of the affected product versions. MongoDB 4.2 has reached end-of-life and contains multiple known security vulnerabilities. An attacker who successfully exploits these vulnerabilities could potentially access sensitive information, cause denial of service, or disrupt system availability.

Zusammenfassung der Gegenmaßnahmen

ABB recommends the following mitigation measures: - Replace bundled MongoDB with a supported version if IIoT services are required: - Where IIoT functionality is required, the bundled MongoDB instance can be replaced with a supported and patched version through manual configuration. - The following zenon online help section explains the process of installing and using your own MongoDB database: zenHelpViewer - Uninstall IIoT Services wherever it’s not required: - If IIoT Services are not required, they can be removed using the Control panel uninstaller. This eliminates the dependency on MongoDB without affecting other zenon components. Refer to section “General security recommendations” for further advise on how to keep your system secure.

Risk Evaluation

ABB has been contacted by a researcher who identified a vulnerability in one of its products. ABB has been contacted by a researcher who identified a vulnerability in one of its products. The vulnerability report has been shared in responsible disclosure. An attacker who successfully exploited this vulnerability could cause the product to become unusable. ABB confirms the vulnerability but at the same time acknowledges that the issue affects exclusively classic KNX devices that are not supporting the latest KNX Secure standard. Due to a lack of security in legacy KNX devices, the issue cannot be resolved via a software change. In order to actively exploit this vulnerability, an attacker requires physical access to the bus, the affected device is connected to. ABB has no plans of corrective measures.

Zusammenfassung der Gegenmaßnahmen

Due to the nature of the classic KNX protocol stack and security concept, there are no options to resolve the vulnerability with a software update on a technical level. ABB recommends to follow general security recommendations listed in the security guideline (see References and General security recommendations). In addition, it shall be avoided to control sensitive functionality by legacy KNX devices such as, but not limited to, access control to e.g. hotel rooms or other protected areas. Note: Legacy KNX standards were never designed to meet state of the art security standards like introduced with KNX Data Secure published in 2017.

Risk Evaluation

ABB has been contacted by a researcher who identified a vulnerability in one of its products. ABB has been contacted by a researcher who identified a vulnerability in one of its products. The vulnerability report has been shared in responsible disclosure. An attacker who successfully exploited this vulnerability could cause the product to become unusable. ABB confirms the vulnerability but at the same time acknowledges that the issue affects exclusively classic KNX devices that are not supporting the latest KNX Secure standard. Due to a lack of security in legacy KNX devices, the issue cannot be resolved via a software change. In order to actively exploit this vulnerability, an attacker requires physical access to the bus, the affected device is connected to. ABB has no plans of corrective measures.

Zusammenfassung der Gegenmaßnahmen

Due to the nature of the classic KNX protocol stack and security concept, there are no options to resolve the vulnerability with a software update on a technical level. ABB recommends to follow general security recommendations listed in the security guideline (see References and General security recommendations). In addition, it shall be avoided to control sensitive functionality by legacy KNX devices such as, but not limited to, access control to e.g. hotel rooms or other protected areas. Note: Legacy KNX standards were never designed to meet state of the art security standards like introduced with KNX Data Secure published in 2017.

Risk Evaluation

The vulnerability enables unauthorized access to the Reboot OS function within the Remote Transport Service, allowing an attacker to trigger a system reboot without the required authentication. This functionality initiates a system reboot on the target machine. However, remote exploitation of this vulnerability is not feasible unless the attacker has already gained access to the network where the affected ABB Ability™ zenon system is deployed. At the time of writing, there is no evidence that this vulnerability is being actively exploited in the wild.

Zusammenfassung der Gegenmaßnahmen

- Restrict network access to systems with the ABB zenon Software Platform installed. - Ensure that access to a system is restricted by implementing access controls to minimize the risk of unauthorized access. - Assess the necessity of the ABB zenon Remote Transport functionality. - Ensure that if the Remote Transport functionality is not used, the zensyssrv.exe (ABB zenon System Service) is stopped or terminated. The zensyssrv.exe can also be stopped or terminated after authorized use to prevent this vulnerability.

Risk Evaluation

ABB is aware of public reports of a vulnerability CVE‑2026‑31431 (Copy Fail) in the product versions listed as affected in the advisory. An update is available that resolves a publicly reported vulnerability. CVE‑2026‑31431 (Copy Fail) is a Linux kernel vulnerability that may allow a locally authenticated user or compromised container workload to gain elevated (root) privileges on affected systems. Once root access is obtained, the attacker can effectively gain complete control of the system

Zusammenfassung der Gegenmaßnahmen

The problem is corrected in the following product versions: - Edgenius 3.2.4.1 ABB recommends that customers apply the update at earliest convenience.

Risk Evaluation

ABB became aware of vulnerability in the products versions listed as affected in the advisory, where an incorrect version of Online Builder (ONB) was included in the media. An update is available that resolves the vulnerability, see details in Recommended immediate actions.

Zusammenfassung der Gegenmaßnahmen

ABB has investigated the vulnerability and remediated it in the newly released versions. The vulnerability has been resolved in the product versions listed as fixed in the advisory. - Version 6.1.1-2 does not contain this vulnerability and therefore no update is required. The vulnerability was again introduced in 6.1.1-3 when an older ONB version was included in the release media. - Version 6.1.1-4 do not contain this vulnerability but present version 6.1.1-3 by 800xA System Installer and System Configuration Console (SCC). Version 6.1.1-4 is therefore withdrawn. - Version 6.2.0-2 do not contain this vulnerability but present version 6.2.0-1 by 800xA System Installer and System Configuration Console (SCC). Version 6.2.0-2 is therefore withdrawn. ABB recommends that customers apply the update at their earliest convenience. - Control Builder A: It is recommended to update Control Builder A to version 1.4/5 or later. - 800xA for Advant Master: - Versions 6.0.3-1 and earlier, - Versions 6.1.1-1 and earlier, - Versions 6.1.1-2, 6.1.1-3, and 6.1.1-4 should be updated to version 6.1.1-5 or later. - 800xA for Advant Master: - Versions 6.2.0-1 and 6.2.0-2 should be updated to version 6.2.0-3 or later.