Successful exploitation of these remotely exploitable vulnerabilities, discovered by Tom Westenberg of Thales UK, could allow an attacker to escalate unnecessary privileges and use hard-coded credentials to take control of the device.
The following MU320E firmware suffers from the issue: All versions prior to v04A00.1
In one issue, the software contains a hard-coded password that could allow an attacker to take control of the merging unit using these hard-coded credentials.
CVE-2021-27452 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 9.8.
In addition, a miscommunication in the file system allows adversaries with access to the MU320E to escalate privileges.
CVE-2021-27448 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.8.
Also, SSH server configuration file does not implement some best practices. This could lead to a weakening of the SSH protocol strength, which could lead to additional misconfiguration or be leveraged as part of a larger attack.
CVE-2021-27450 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 3.8.
The product sees use in multiple industrial sectors, and on a global basis.
No known public exploits specifically target these vulnerabilities. However, an attacker with low skill level could leverage the vulnerabilities.
GE recommends MU320E users upgrade to firmware v04A00.1 or higher to mitigate these vulnerabilities.
Instructions on how to upgrade the MU320E firmware and verify its installation are available in the product user’s manual.
See GE publication number: GES-2021-003 for more information.
GE recommends MU320E devices be protected using network defense-in-depth practices. This includes, but is not limited to, placing MU320E devices inside the control system network security perimeter, and having access controls, monitoring (such as an Intrusion Detection System), and other mitigating technologies in place. Quite a few electric utilities have deployed cyber security solutions in accordance with the NERC-CIP implementation requirements. Please refer to the product secure deployment guide.

