telnetd in GNU Inetutils through 2.7 allows remote authentication bypass via a "-f root" value for the USER environment variable.

(Source: www.cve.org)

• Insufficient protection for credentials in Intel® AMT and Intel® Standard Manageability may allow an unauthenticated user to potentially enable information disclosure and escalation of privilege via network access (CVE-2022-30601).
• Insufficient protection for credentials in Intel® AMT and Intel® Standard Manageability may allow a privileged user to potentially enable information disclosure via local access (CVE-2022-30944).
• Improper access control in firmware for Intel® AMT and Intel® Standard Manageability may allow an unauthenticated user to potentially enable escalation of privilege via physical access (CVE-2022-28697).

(Source: Tenable Nessus)

Since this is a critical severity issue, users are strongly advised to immediately apply the solutions to mitigate associated security risks.

• Out-of-bounds write in IPv6 subsystem for Intel(R) AMT, Intel® ISM versions before 11.8.80, 11.12.80, 11.22.80, 12.0.70, and 14.0.45 may allow an unauthenticated user to potentially enable escalation of privileges via network access. (CVE-2020-8752)
• Out-of-bounds read in subsystem for Intel® AMT versions before 11.8.80, 11.12.80, 11.22.80, 12.0.70, and 14.0.45 may allow an unauthenticated user to potentially enable information disclosure and/or denial of service via network access. (CVE-2020-8747)
• Out-of-bounds read in subsystem for Intel® AMT versions before 11.8.80, 11.12.80, 11.22.80, 12.0.70, and 14.0.45 may allow an unauthenticated user to potentially enable escalation of privilege via adjacent access. (CVE-2020-8749)

(Source: Tenable Nessus)

Since this is a critical severity issue, users are strongly advised to immediately apply the solutions to mitigate associated security risks.

Since this is a medium severity issue, users can assess their environment and adopt the solution during the next maintenance cycle.

CVE-2026-0714

A physical attack vulnerability exists in certain Moxa industrial computers using TPM-backed LUKS full-disk encryption on Moxa Industrial Linux 3, where the discrete TPM is connected to the CPU via an SPI bus. Exploitation requires invasive physical access, including opening the device and attaching external equipment to the SPI bus to capture TPM communications. If successful, the captured data may allow offline decryption of eMMC contents. This attack cannot be performed through brief or opportunistic physical access and requires extended physical access, possession of the device, appropriate equipment, and sufficient time for signal capture and analysis. Remote exploitation is not possible.

CVE-2026-0715

Moxa Arm-based industrial computers running Moxa Industrial Linux Secure use a device-unique bootloader password provided on the device. An attacker with physical access to the device could use this information to access the bootloader menu via a serial interface.  Access to the bootloader menu does not allow full system takeover or privilege escalation. The bootloader enforces digital signature verification and only permits flashing of Moxa-signed images. As a result, an attacker cannot install malicious firmware or execute arbitrary code. The primary impact is limited to a potential temporary denial-of-service condition if a valid image is reflashed. Remote exploitation is not possible.

Given the high severity of these issues, users should apply the solutions immediately to reduce security risks.

The Identified Vulnerability Type and Potential Impact 

Vulnerability Scoring Details 

Since this issue is considered high severity, users should immediately apply the solutions to mitigate associated security risks.

The Identified Vulnerability Type and Potential Impact

Vulnerability Scoring Details 

CVE-2023-38408

Because of an unreliable search path, the PKCS#11 feature in OpenSSH’s ssh-agent before 9.3p2 allows remote code execution if an agent is sent to a system controlled by an attacker. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: This issue exists because of an incomplete fix for CVE-2016-10009. (Source: cve.org)

CVE-2023-38408 is related to the SSH agent component and can only be exploited when SSH agent forwarding is enabled. However, in typical deployment scenarios, Moxa's ethernet switches operate as SSH servers and does not enable `ssh-agent` or agent forwarding functionality. Therefore, the practical risk is considered very low because the conditions required to trigger this vulnerability are not present by default. This issue is considered low risk, users may evaluate their environments and decide if updating is required.

The Identified Vulnerability Type and Potential Impact 

Vulnerability Scoring Details 

CVE-2025-15017

A vulnerability exists in serial device servers where active debug code remains enabled in the UART interface. An attacker with physical access to the device can directly connect to the UART interface and, without authentication, user interaction, or execution conditions, gain unauthorized access to internal debug functionality. Exploitation is low complexity and allows an attacker to execute privileged operations and access sensitive system resources, resulting in a high impact to the confidentiality, integrity, and availability of the affected device. No security impact to external or dependent systems has been identified.

Since this issue is considered high severity, users should immediately apply the solutions to mitigate associated security risks.

The Identified Vulnerability Type and Potential Impact

Vulnerability Scoring Details 

CVE-2025-1977

The NPort 6100-G2/6200-G2 Series is affected by an execution with unnecessary privileges vulnerability (CVE-2025-1977) that allows an authenticated user with read-only access to perform unauthorized configuration changes through the MCC (Moxa CLI Configuration) tool. The issue can be exploited remotely over the network with low-attack complexity and no user interaction but requires specific system conditions or configurations to be present. Successful exploitation may result in changes to device settings that were not intended to be permitted for the affected user role, potentially leading to a high impact on the confidentiality, integrity, and availability of the device. No impact on other systems has been identified.

CVE-2025-2026

The NPort 6100-G2/6200-G2 Series is affected by a high-severity vulnerability (CVE-2025-2026) that allows remote attackers to execute a null byte injection through the device’s web API. This may lead to an unexpected device reboot and result in a denial-of-service (DoS) condition.

Since these issues have high severity, we strongly advise users to immediately apply the solutions to mitigate associated security risks.
 

The Identified Vulnerability Type and Potential Impact

Vulnerability Scoring Details 

Since this is a medium severity issue, users can assess their environment and schedule the update during the next maintenance or update cycle.

CVE-2025-9315

An unauthenticated device registration vulnerability, caused by Improperly Controlled Modification of Dynamically-Determined Object Attributes, has been identified in the MXsecurity Series. An unauthenticated remote attacker can exploit this vulnerability by sending a specially crafted JSON payload to the device's registration endpoint /api/v1/devices/register, allowing the attacker to register unauthorized devices without authentication. Although exploiting this vulnerability has limited modification of data, there is no impact to the confidentiality and availability of the affected device, as well as no loss of confidentiality, integrity, and availability within any subsequent systems.

Because the vulnerability is assessed as medium severity, users are suggested to evaluate their environment and schedule the update in the next maintenance or update cycle.

The Identified Vulnerability Type and Potential Impact

Vulnerability Scoring Details 

Since this is a medium severity issue, users can assess their environment and schedule the update during the next maintenance or update cycle.

Because the issue is assessed as low severity, users can evaluate their environments and decide if an update is required.

Because the issue has low severity, users can assess their environments and decide if an update is needed.

As this issue is assessed as low severity, users may evaluate their environments and decide if updating is required.

CVE-2025-1679

Cross-site Scripting has been identified in Moxa’s Ethernet switches, which allows an authenticated administrative attacker to inject malicious scripts to an affected device’s web service that could impact authenticated users interacting with the device’s web interface. This vulnerability is classified as stored cross-site scripting (XSS); attackers inject malicious scripts into the system, and the scripts persist across sessions. There is no impact to the confidentiality, integrity, and availability of the affected device; no loss of availability within any subsequent systems but has some loss of confidentiality and integrity within the subsequent system.

CVE-2025-1680

An acceptance of extraneous untrusted data with trusted data vulnerability has been identified in Moxa’s Ethernet switches, which allows attackers with administrative privileges to manipulate HTTP Host headers by injecting a specially crafted Host header into HTTP requests sent to an affected device’s web service. This vulnerability is classified as Host Header Injection, where invalid Host headers can manipulate to redirect users, forge links, or phishing attacks. There is no impact to the confidentiality, integrity, and availability of the affected device; no loss of confidentiality, integrity, and availability within any subsequent systems.

Because the issues are assessed as medium to low severity, users can evaluate their environment and schedule the update in the next maintenance or update cycle.

The Identified Vulnerability Type and Potential Impact

Vulnerability Scoring Details 

As this issue is assessed as medium severity, users may evaluate their environment and schedule the update in the next maintenance or update cycle.

As this issue is assessed as medium severity, users may evaluate their environment and schedule the update in the next maintenance or update cycle.

As this issue is assessed as high severity, users are strongly advised to immediately apply the solutions to mitigate associated security risks.

As this issue is assessed as low severity, users may evaluate their environments and decide if updating is required.

As this issue is assessed as low severity, users may evaluate their environments and decide if updating is required.

As this issue is assessed as low severity, users may evaluate their environments and decide if updating is required.

As this issue is assessed as low severity, users may evaluate their environments and decide if updating is required.

CVE-2025-6892

An Incorrect Authorization vulnerability has been identified in Moxa’s network security appliances and routers. A flaw in the API authentication mechanism allows unauthorized access to protected API endpoints, including those intended for administrative functions. This vulnerability can be exploited after a legitimate user has logged in, as the system fails to properly validate session context or privilege boundaries. An attacker may leverage this flaw to perform unauthorized privileged operations. While successful exploitation can severely impact the confidentiality, integrity, and availability of the affected device itself, there is no loss of confidentiality or integrity within any subsequent systems.

CVE-2025-6893

An Execution with Unnecessary Privileges vulnerability has been identified in Moxa’s network security appliances and routers. A flaw in broken access control has been identified in the /api/v1/setting/data endpoint of the affected device. This flaw allows a low-privileged authenticated user to call the API without the required permissions, thereby gaining the ability to access or modify system configuration data. Successful exploitation may lead to privilege escalation, allowing the attacker to access or modify sensitive system settings. While the overall impact is high, there is no loss of confidentiality or integrity within any subsequent systems.

CVE-2025-6894

An Execution with Unnecessary Privileges vulnerability has been identified in Moxa’s network security appliances and routers. A flaw in the API authorization logic of the affected device allows an authenticated, low-privileged user to execute the administrative `ping` function, which is restricted to higher-privileged roles. This vulnerability enables the user to perform internal network reconnaissance, potentially discovering internal hosts or services that would otherwise be inaccessible. Repeated exploitation could lead to minor resource consumption. While the overall impact is limited, it may result in some loss of confidentiality and availability on the affected device. There is no impact on the integrity of the device, and the vulnerability does not affect any subsequent systems.

CVE-2025-6949

An Execution with Unnecessary Privileges vulnerability has been identified in Moxa’s network security appliances and routers. A critical authorization flaw in the API allows an authenticated, low-privileged user to create a new administrator account, including accounts with usernames identical to existing users. In certain scenarios, this vulnerability could allow an attacker to gain full administrative control over the affected device, leading to potential account impersonation. While successful exploitation can severely impact the confidentiality, integrity, and availability of the affected device itself, there is no loss of confidentiality or integrity within any subsequent systems.

CVE-2025-6950

An Use of Hard-coded Credentials vulnerability has been identified in Moxa’s network security appliances and routers. The system employs a hard-coded secret key to sign JSON Web Tokens (JWT) used for authentication. This insecure implementation allows an unauthenticated attacker to forge valid tokens, thereby bypassing authentication controls and impersonating any user. Exploitation of this vulnerability can result in complete system compromise, enabling unauthorized access, data theft, and full administrative control over the affected device. While successful exploitation can severely impact the confidentiality, integrity, and availability of the affected device itself, there is no loss of confidentiality or integrity within any subsequent systems.

Given the severity of these vulnerabilities, users are strongly advised to apply the latest firmware updates immediately to mitigate associated security risks.

The Identified Vulnerability Type and Potential Impact

Vulnerability Scoring Details 

(Source: Tenable Nessus)

To enhance the security of the product, users should implement appropriate mitigations or solutions to avoid potential security issue.

(Source: CVE-2016-2183)

To enhance the security of the product, users should implement appropriate mitigations or solutions to avoid potential security issue.

CVE-2025-5191

An Unquoted Search Path vulnerability has been identified in the utility for Moxa’s industrial computers (Windows). Due to the unquoted path configuration in the SerialInterfaceService.exe utility, a local attacker with limited privileges could place a malicious executable in a higher-priority directory within the search path. When the Serial Interface service starts, the malicious executable could be run with SYSTEM privileges. Successful exploitation could allow privilege escalation or enable an attacker to maintain persistence on the affected system. While successful exploitation can severely impact the confidentiality, integrity, and availability of the affected device itself, there is no loss of confidentiality, integrity, or availability within any subsequent systems.

Given the severity of the vulnerability, users are strongly advised to immediately apply the latest version of the utility that includes a fix for this issue to mitigate associated security risks.

The Identified Vulnerability Type and Potential Impact

Vulnerability Scoring Details 

The Diffie-Hellman Key Agreement Protocol allows remote attackers (from the client side) to send arbitrary numbers that are actually not public keys and trigger expensive server-side DHE modular-exponentiation calculations, also known as a D(HE)at or D(HE)ater attack. The client needs very little CPU resources and network bandwidth. The attack may be more disruptive where a client can require a server to select its largest supported key size. The basic attack scenario requires the client to claim DHE-only communication capabilities, and the server must be configured to permit DHE. 

This vulnerability affects any product or service that accepts DHE cipher suites. To mitigate the risk, Moxa has released solutions for the affected products. We recommend applying the appropriate solutions immediately. 

The Identified Vulnerability Type and Potential Impact 

Vulnerability Scoring Details 

To mitigate these risks, Moxa has released solutions for the affected products. It is strongly recommended to update to the latest version as soon as possible. 

The identified vulnerability types and potential impacts are listed below:

Vulnerability Scoring Details 

To mitigate these risks, Moxa has released solutions for the affected products. It is strongly recommended to update to the latest version as soon as possible. 

The identified vulnerability types and potential impacts are listed below:

Vulnerability Scoring Details 

The Identified Vulnerability Type and Potential Impact 

Vulnerability Scoring Details 

This vulnerability poses a significant remote threat if the affected products are exposed to publicly accessible networks. Attackers could potentially disrupt operations by shutting down the affected systems. Given the severity of this issue, immediate action is strongly recommended to mitigate potential exploitation. 

The Identified Vulnerability Type and Potential Impact 

Vulnerability Scoring Details 

Note: This advisory uses CVSS 3.1 as the standard for determining severity levels. CVSS 4.0 is provided as a reference metric for comparison. 

This vulnerability poses a significant remote threat if the affected products are exposed to publicly accessible networks. Attackers could potentially disrupt operations by shutting down the affected systems. Given the severity of this issue, immediate action is strongly recommended to mitigate potential exploitation. 

The Identified Vulnerability Type and Potential Impact 

Vulnerability Scoring Details 

Note: This advisory uses CVSS 3.1 as the standard for determining severity levels. CVSS 4.0 is provided as a reference metric for comparison.

This vulnerability poses a significant remote threat if the affected products are exposed to publicly accessible networks. Attackers could potentially disrupt operations by shutting down the affected systems. Due to the critical nature of this security risk, we strongly recommend taking immediate action to prevent its potential exploitation. 

The Identified Vulnerability Type and Potential Impact 

Vulnerability Scoring Details 

Note: This advisory uses CVSS 3.1 as the standard for determining severity levels. CVSS 4.0 is provided as a reference metric for comparison. 

This vulnerability poses a significant remote threat if the affected products are exposed to publicly accessible networks. Attackers could potentially disrupt operations by shutting down the affected systems. Due to the critical nature of this security risk, we strongly recommend taking immediate action to prevent its potential exploitation. 

The Identified Vulnerability Type and Potential Impact 

Vulnerability Scoring Details 

Note: This advisory uses CVSS 3.1 as the standard for determining severity levels. CVSS 4.0 is provided as a reference metric for comparison. 

This vulnerability poses a significant remote threat if the affected products are exposed to publicly accessible networks. Attackers could potentially disrupt operations by shutting down the affected systems. Due to the critical nature of this security risk, we strongly recommend taking immediate action to prevent its potential exploitation. 

The Identified Vulnerability Type and Potential Impact 

Vulnerability Scoring Details 

Note: This advisory uses CVSS 3.1 as the standard for determining severity levels. CVSS 4.0 is provided as a reference metric for comparison. 

The identified vulnerability types and potential impacts are listed below:

Vulnerability Scoring Details 

Note: This advisory uses CVSS 3.1 as the standard for determining severity levels. CVSS 4.0 is provided as a reference metric for comparison.

The Identified Vulnerability Type and Potential Impact 

Vulnerability Scoring Details 

The identified vulnerability types and potential impacts are listed below:

Vulnerability Scoring Details 

• SNMP Agent Default Community Name (public) 
• SNMP ‘GETBULK’ Reflection DDoS 

• Unencrypted Telnet Server 

• SSL Certificate Cannot Be Trusted 
• SSL Certificate Chain Contains RSA Keys Less Than 2048 Bits 

• CVE-2024-9138: This vulnerability involves hard-coded credentials, which could allow an authenticated user to escalate privileges and gain root-level access to the system.
• CVE-2024-9140: This vulnerability allows attackers to exploit special characters to bypass input restrictions, potentially leading to unauthorized command execution.

Immediate action is strongly recommended to prevent potential exploitation and mitigate these risks.

The identified vulnerability types and potential impacts are listed below:

Vulnerability Scoring Details 

Note: This advisory uses CVSS 3.1 as the standard for determining severity levels. CVSS 4.0 is provided as a reference metric for comparison.

TN-G4500 Series has enhanced its cryptographic algorithm and cipher suite.

This vulnerability poses a significant remote threat if the affected products are exposed to publicly accessible networks. Attackers could potentially disrupt operations by shutting down the affected systems. Due to the critical nature of this security risk, we strongly recommend taking immediate action to prevent potential exploitation.

The Identified Vulnerability Type and Potential Impact

Vulnerability Scoring Details 

1. Modbus/TCP Coil Access: Attackers could read and analyze coil settings, which may allow them to alter device functions in SCADA and DCS environments.
2. Modbus/TCP Device Identification: Attackers could retrieve device details via Modbus MEI read requests, potentially exposing Vendor Name, Product Code, and other identifying information.
3. Unencrypted Telnet Server: Using Telnet over an unencrypted channel can expose sensitive information, such as credentials, to interception. SSH is recommended as a secure alternative.

These updates aim to improve the EDS-P510 Series’ resilience against vulnerabilities, thereby enhancing its overall security.

Vulnerability Scoring Details 

The identified vulnerability types and potential impacts are listed below:

Vulnerability Scoring Details 

The identified vulnerability types and potential impacts are listed below:

Vulnerability Scoring Details 

The Identified Vulnerability Type and Potential Impact

Vulnerability Scoring Details 

CVE-2024-4739 

The lack of access restriction to a resource from unauthorized users makes MXsecurity software versions v1.1.0 and prior vulnerable. By acquiring a valid authenticator, an attacker can pose as an authorized user and successfully access the resource. 

CVE-2024-4740 

MXsecurity software versions v1.1.0 and prior are vulnerable because of the use of hard-coded credentials. This vulnerability could allow an attacker to tamper with sensitive data. 

The identified vulnerability types and potential impacts are shown below: 

Vulnerability Scoring Details 

The identified vulnerability types and potential impacts are listed below:

Vulnerability Scoring Details 

The Identified Vulnerability Type and Potential Impact

Vulnerability Scoring Details 

The identified vulnerability types and potential impacts are listed below:

Note: An asterisk (*) in the table above indicates newly assigned Common Vulnerabilities and Exposures (CVE) identifiers.

Vulnerability Scoring Details

The identified vulnerability types and potential impacts are listed below:

Vulnerability Scoring Details 

The identified vulnerability types and potential impacts are listed below:

Vulnerability Scoring Details 

Vulnerability Scoring Details 

Vulnerability Scoring Details 

Vulnerability Scoring Details 

Vulnerability Scoring Details 

Vulnerability Scoring Details 

Vulnerability Scoring Detail

The identified vulnerability types and potential impacts are shown below:

CVE-2023-5961

A vulnerability has been identified in ioLogik E1200 Series firmware versions v3.3 and prior. An attacker can exploit this vulnerability to trick a client into making an unintentional request to the web server, which will be treated as an authentic request.

CVE-2023-5962

A vulnerability has been identified in ioLogik E1200 Series firmware versions v3.3 and prior. This vulnerability can help an attacker compromise the confidentiality of sensitive data.

The identified vulnerability types and potential impacts are shown below:

The identified vulnerability types and potential impacts are shown below:

The identified vulnerability types and potential impacts are shown below:

The identified vulnerability type and potential impact are shown below: 

Vulnerability Scoring Details

The identified vulnerability types and potential impacts are shown below: 

Security Enhancements

1. Cryptographic Key
   Increases the RSA key length from 1024 to 2048.
2. Static Key Ciphers
   Removes medium strength cipher suites TLS_RSA_WITH_AES_128_CBC_SHA and TLS_RSA_WITH_AES_128_GCM_SHA256.
3. Strong Cipher Algorithms
   Uses strong cipher suites ECDHE-RSA-AES128-SHA256 and ECDHE-RSA-AES128-GCM-SHA256.

The identified vulnerability types and potential impacts are shown below:

Web Server Vulnerabilities 

The web server vulnerabilities arise from improper configuration or implementation of HTTP headers. Attackers could exploit the vulnerabilities to compromise the web service. 

Improper Access Control Vulnerability 

The improper access control vulnerability results from improper control of an existing unauthorized service. Attackers could exploit the vulnerability by connecting to the unauthorized service. Successful exploitation of the vulnerability could lead to unauthorized access. 

The identified vulnerability types and potential impacts are shown below: 

A vulnerability has been identified in NPort IAW5000A-I/O Series firmware versions prior to v2.2, which poses a potential risk to the security and integrity of the affected device. 

The identified vulnerability types and potential effects are shown below: 

The identified vulnerability types and potential impacts are shown below:

Moxa has investigated the vulnerability and has determined that it affects some of Moxa's devices. In response to this, Moxa has developed solutions to address this vulnerability. Please refer to the Affected Products and Solutions section below to learn more.

CVE-2023-33236 (ZDI-CAN-19896)
A vulnerability has been reported that can be exploited to craft arbitrary JWT tokens and subsequently bypass authentication for web-based APIs.

The identified vulnerability types and potential impacts are shown below:

An out-of-bounds write vulnerability exists in TPM 2.0's Module Library allowing writing of a 2-byte data past the end of TPM 2.0 command in the CryptParameterDecryption routine. An attacker who can successfully exploit this vulnerability can execute a denial of service (crashing the TPM chip/process or rendering it unusable) and/or perform arbitrary code execution in the TPM context. 

CVE-2023-1018 

An out-of-bounds read vulnerability exists in TPM 2.0's Module Library allowing a 2-byte read past the end of a TPM 2.0 command in the CryptParameterDecryption routine. An attacker who can successfully exploit this vulnerability can read or access sensitive data stored in the TPM. 

Moxa is investigating to determine if any of our products are affected by this vulnerability. At the time of publication, none of Moxa’s products are affected. 

Moxa's Product Security Incident Response Team (PSIRT) will keep monitoring the situation and if there are any updates to the status of the vulnerability that affects Moxa's products, we will provide an update immediately. 

The Windows driver manager software does not perform any certificate verification. 

There is no client certificate verification/authentication performed on the secure connection. 

The identified vulnerability types and potential impacts are shown below:

Moxa is investigating to determine if any of our products are affected by this vulnerability. At the time of publication, none of Moxa’s products are affected.

Moxa's Product Security Incident Response Team (PSIRT) will keep monitoring the situation and if there are any updates to the status of the vulnerability that affects Moxa's products, we will provide an update immediately.

Moxa is investigating to determine if any of our products are affected by this vulnerability. At the time of publication, none of Moxa’s products are affected.

Moxa's Product Security Incident Response Team (PSIRT) will keep monitoring the situation and if there are any updates to the status of the vulnerability that affects Moxa's products, we will provide an update immediately.

In order for this vulnerability to be exploited, an attacker has to use a cable to access the device’s bootloader menu. Therefore, the device is vulnerable if it is deployed in an area without proper physical security (e.g., in an open space without access control).

Moxa’s PSIRT would like to remind organizations to perform a proper impact analysis and risk assessment prior to deploying defensive measures, such as the security patch.

The identified vulnerability types and potential impacts are shown below:

The identified vulnerability types and potential impacts are shown below:

Moxa is investigating to determine if any of our products are affected by this vulnerability. At the time of publication, none of Moxa’s products are affected.

Moxa's Product Security Incident Response Team (PSIRT) will keep monitoring the situation and if there are any updates to the status of the vulnerability that affects Moxa's products, we will provide an update immediately.

Moxa is investigating to determine if any of our products are affected by this vulnerability. At the time of publication, none of Moxa’s products are affected.

Moxa's Product Security Incident Response Team (PSIRT) will keep monitoring the situation and if there are any updates to the status of the vulnerability that affects Moxa's products, we will provide an update immediately.

The identified vulnerability types and potential impacts are shown below:

Moxa is investigating to determine if any of our products are affected by this vulnerability. At the time of publication, none of Moxa’s products are affected.

Moxa's Product Security Incident Response Team (PSIRT) will keep monitoring the situation and if there are any updates to the status of the vulnerability that affects Moxa's products, we will provide an update immediately.

At the time of publication, none of Moxa’s products are affected by these vulnerabilities.

Moxa's Product Security Incident Response Team (PSIRT) will keep monitoring the situation and if there are any updates to the status of the vulnerability that affects Moxa's products, we will provide an update immediately.

Moxa has investigated the vulnerabilities and has determined that the vulnerabilities affect AWK-3131A/4131A/1137C/1131A Series. In response to this, Moxa has developed related solutions to address these vulnerabilities.
 

The identified vulnerability types for ioAdmin Configuration Utility and potential impacts are shown below:

Moxa has investigated this vulnerability and has determined that none of our products are affected.

Moxa's Cyber Security Response Team (CSRT) will keep monitoring the situation and if there are any updates to the status of the vulnerability that affects Moxa's products, an update will be provided immediately.

The identified vulnerability types and potential impacts are shown below:

OnCell G3100-HSPA Series:

The identified vulnerability type and potential impacts is shown below:

The identified vulnerability types and potential impacts are shownbelow:

The identified vulnerability types and potential impacts are shown below:

EDS-405A Series, EDS-408A Series, and EDS-510A Series

IKS-G6824A Series

The identified vulnerability types and potential impacts are shown below:

Moxa has investigated and has not found any products that are affected by these vulnerabilities.

Moxa's Cyber Security Response Team (CSRT) will keep monitoring the situation and if there are any updates to the status of the vulnerabilities and it would affect Moxa's products, an update will be provided immediately.

The identified vulnerability types and potential impacts are shown below:

The identified vulnerability type and potential impact are shown below:

• CVE-2017-5689

In the second half of 2017, researchers identified multiple vulnerabilities that are related to the Intel Management Engine.

• CVE-2017-5705

• CVE-2017-5708

• CVE-2017-5711

• CVE-2017-5712

In response to these vulnerabilities, Intel released a patch management engine firmware for all its platforms. Moxa has identified which of our products have been affected and issued a firmware upgrade. Any products that are not listed will not be affected by the aforementioned vulnerabilities. We recommend that people who have purchased the affected products get assistance through Moxa Global Customer Service and update to the latest BIOS.

The identified vulnerability type and potential impact are shown below:

The identified vulnerability types and potential impacts are shown below:

The identified vulnerability types and potential impacts are shown below:

The identified vulnerability type and potential impact are shown below:

The identified vulnerability types and potential impacts are shown below:

The identified vulnerability type and potential impact are shown below:

CVE-2017-5753 (Spectre)
CVE-2017-5715 (Spectre)
CVE-2017-5754 (Meltdown)

The vulnerabilities could allow an attacker to read information on the microprocessors or memory allocated on the operating system kernel.

To take advantage of these vulnerabilities, the attacker must be able to run a malicious custom code on a device. The vast majority of Moxa's products are not vulnerable since they operate on closed systems that do not allow custom codes to be run on the devices.

Moxa's devices that use a computer platform which includes microprocessors that could be targeted may be considered vulnerable even if they are not directly affected by the vulnerabilities. Vendors of microprocessors and operating systems are releasing updates that help mitigate these vulnerabilities. Moxa will also release updates for these products based on the vendor's suggestions.

Moxa's Cyber Security Response Team (CSRT) is fully engaged in this matter and we are taking appropriate action. If there are any updates to the status of the vulnerabilities or how these affect Moxa's products, we will provide an update immediately.

Moxa's Cyber Security Response Team (CSRT) is fully engaged in this matter and we are taking appropriate action. Our team has been working with all of our product teams to determine which models have been affected.

The identified vulnerability types and potential impacts are shown below:

The identified vulnerability types and potential impacts are shown below:

The identified vulnerability types and potential impacts are shown below:

The identified vulnerability types and potential impacts are shown below:

The identified vulnerability types and potential impacts are shown below:

ICS-CERT recommends the three following general defensive measures to protect against this and other cybersecurity risks:

• Minimize network exposure for all control system devices and/or systems, and ensure that they are not accessible from the Internet.
• Locate control system networks and remote devices behind firewalls, and isolate them from the business network.
• When remote access is required, use secure methods, such as Virtual Private Networks (VPNs), recognizing that VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize that VPN is only as secure as the connected devices.

Moxa's Cyber Security Response Team (CSRT) is fully engaged in this matter and we are taking appropriate action. If there are any updates to the status of the vulnerabilities or how these affect Moxa's products, we will provide an update immediately.

Moxa's Cyber Security Response Team (CSRT) is fully engaged in this matter and we are taking appropriate action. If there are any updates to the status of the vulnerabilities or how these affect Moxa's products, we will provide an update immediately.

Moxa's Cyber Security Response Team (CSRT) is fully engaged in this matter and we are taking appropriate action. If there are any updates to the status of the vulnerabilities or how these affect Moxa's products, we will provide an update immediately.