title: GE Gas Power ToolBoxST Improper Restriction of XML External Entity Reference
description: GE Gas Power ToolBoxST Version v04.07.05C suffers from an XML external entity (XXE) vulnerability using the DTD parameter entities technique that could result in disclosure and retrieval of arbitrary data on the affected node via an out-of-band (OOB) attack. The vulnerability is triggered when input passed to the XML parser is not sanitized while parsing the XML project/template file.
problem types: CWE-611 Improper Restriction of XML External Entity Reference ('XXE')
affected:
{
product: ToolBoxST
vendor: GE Gas Power
versions:
lessThan: 07.09.07C, status: affected, version: unspecified, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: NONE
baseScore: 7.5
baseSeverity: HIGH
confidentialityImpact: HIGH
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
version: 3.1
]
solutions: GE addressed CVE-2021-44477 in ToolBoxST OS Version 07.09.07C and above by disabling the use of DTD’s, which are not necessary for ToolBoxST functionality.
GE upgraded the Ionic library in ToolBoxST Version 7.8.0 to resolve CVE-2018-16202
Users should ensure they follow the password protection and network segmentation guidance laid out in GEH-6839 Secure Deployment Guide. Additionally, the use of SDI Secure Mode offers considerable protection against this attack as the threat actor must be able to perform a download to the controller over SDI. Secure Mode validates authenticity and protects against spoofing of SDI commands.
workarounds: GE Gas Power Cybersecurity and Engineering teams will continue to investigate internally as well as monitor industry-based news for any changes or updates. To reduce the risk vulnerabilities such as these may represent to the controls network, GE recommends the implementation of a good defense-in-depth strategy as detailed in GEH-6839. Some recommended controls include:
Minimize network exposure for all controllers with the use of network segmentation, placement of controllers behind controls network firewalls and ensure they are not accessible from the Internet.
Block suspicious external IP addresses at the controls network firewalls. Monitor traffic internally for unusual behavior.
When remote access is required, use secure methods, such as virtual private networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize VPN is only as secure as its connected devices.
Implement defense-in-depth within the controls network environment consisting of tools such as Intrusion detection/prevention systems (IDS/IPS), firewalls, and network access control (NAC).
Implement and maintain an anti-malware solution and an endpoint detection and response (EDR) solution.
Disable remote access services and protocols such as remote desktop protocol (RDP) unless needed. Monitor and restrict remote access usage on a least-privilege basis.
Have backup and restore processes and procedures in place for disaster recovery and incident response.
Monitor and maintain account provisioning and access control based on the principle of least privilege.