Finding Moxa MXview instances
Security researchers with Claroty’s Team82 recently published findings of five discovered vulnerabilities in Moxa’s MXview software. Focused on “industrial network management”, MXview enables management of deployed Operational Technologies (OT) and Industrial Control Systems (ICS) endpoints.
Which versions of MXview are affected?
These published vulnerabilities reside in the MQTT messaging component of MXview and can be leveraged (and chained together) by an unauthenticated attacker to ultimately gain filesystem access to data (including credentials) or achieve remote code execution on vulnerable systems:
- CVE-2021-38452 (CVSS “critical” score of 9.1) - path traversal vulnerability, may allow an attacker to create or overwrite critical files used to execute code
- CVE-2021-38454 (CVSS “critical” score of 10.0) - path traversal vulnerability, may allow an attacker to create or overwrite critical files used to execute code
- CVE-2021-38456 (CVSS “critical” score of 9.8) - hard-coded password vulnerability, may allow an attacker to gain access through accounts using default passwords
- CVE-2021-38458 (CVSS “critical” score of 9.8) - path traversal vulnerability, may allow an attacker to create or overwrite critical files used to execute code
- CVE-2021-38460 (CVSS “high” score of 7.5) - path traversal vulnerability, may allow an attacker to create or overwrite critical files used to execute code
These vulnerabilities affect MXview versions 3.x to 3.2.2 and were disclosed to Moxa last September (and fixed at that time; associated ICS Advisory here).
An additional two MXview vulnerabilities, discovered by Patrick DeSantis of Cisco’s Talos group, were disclosed last October. These affect all MXview versions up through (and including) 3.2.4, and involve hard-coded credentials and cleartext transmission of sensitive data:
- CVE-2021-40390 (CVSS “critical” score of 10.0) - authentication bypass vulnerability, can lead to unauthorized access
- CVE-2021-40392 (CVSS “medium” score of 5.3) - information disclosure vulnerability, can lead to disclosure of sensitive information via network sniffing
Given the severity of these vulnerabilities (including what can be accomplished via chaining) and the appeal of systems bridging network technologies, vulnerable targets may be of high interest to attackers.
Is an update available?
Yes. Moxa has addressed all of the above vulnerabilities and strongly encourages folks who are running MXview to upgrade to version 3.2.6 or later.
How do I find potentially vulnerable Moxa MXview instances with runZero?
From the Service Inventory, use the following pre-built query to locate Moxa MXview assets within your network that are potentially vulnerable:
_asset.protocol:http and protocol:http and (html.title:"mxview" or last.html.title:"mxview")
As always, any prebuilt queries we create are available from our Queries Library. Check out the library for other useful inventory queries.
Don’t have runZero and need help finding potentially vulnerable MXview instances? Start your runZero trial today.
February 15, 2023
Finding OpenSSH servers
The OpenSSH team surfaced a security issue earlier this month that specifically affects OpenSSH server version 9.1p1 (a.k.a. version 9.1). This version contains a memory double-free vulnerability (tracked as CVE-2023-25136) that can be reached pre-authentication by a remote …Read More
February 8, 2023
Finding VMware ESXi assets
This Rapid Response post covers ESXiArgs, a new strain of ransomware that is targeting VMware ESXi servers. Learn how you can find potentially affected servers on your network.
February 3, 2023
Finding Lexmark printer assets
Printer manufacturer Lexmark recently published details on a vulnerability that affects over 100 of their printer models. Learn how runZero can help you find potentially affected assets.