Softing Secure Integration Server
1. EXECUTIVE SUMMARY
- CVSS v3 7.5
- ATTENTION: Exploitable remotely/low attack complexity
- Vendor: Softing
- Equipment: Secure Integration Server
- Vulnerabilities: Out-of-bounds Read, Uncontrolled Search Path Element, Improper Authentication, Relative Path Traversal, Cleartext Transmission of Sensitive Information, NULL Pointer Dereference, Integer Underflow.
2. RISK EVALUATION
Successful exploitation of these vulnerabilities could allow an attacker to cause a denial-of-service condition.
3. TECHNICAL DETAILS
3.1 AFFECTED PRODUCTS
Softing reports these vulnerabilities affect the following products:
- Secure Integration Server: Version 1.22 and prior
- edgeConnector: Version 3.1
- edgeAggregator: Version 3.1
- OPC UA C++ Server SDK: Version 6
- OPC Suite: Version 5.2
- uaGate: Version 1.74
3.2 VULNERABILITY OVERVIEW
A crafted HTTP packet with a large content-length header can create a denial-of-service condition in Softing Secure Integration Server.
The application searches for a library dll that is not found. If an attacker can place a dll with this name, then the attacker can leverage it to execute arbitrary code on the targeted Softing Secure Integration Server.
Softing Secure Integration Server, edgeConnector, and edgeAggregator software ships with the default administrator credentials as `admin` and password as `admin`. This allows Softing to log in to the server directly to perform administrative functions. Upon installation or upon first login, the application does not ask the user to change the `admin` password. There is no warning or prompt to ask the user to change the default password, and to change the password, many steps are required.
The “restore configuration” feature of Softing Secure Integration Server is vulnerable to a directory traversal vulnerability when processing zip files. An attacker can craft a zip file to load an arbitrary dll and execute code. Using the "restore configuration" feature to upload a zip file containing a path traversal file may cause a file to be created and executed upon touching the disk.
Softing Secure Integration Server is vulnerable to authentication bypass via a machine-in-the-middle attack. The default the administration interface is accessible via plaintext HTTP protocol, facilitating the attack. The HTTP request may contain the session cookie in the request, which may be captured for use in authenticating to the server.
Softing OPC UA C++ Server SDK, Secure Integration Server, edgeConnector, edgeAggregator, OPC Suite, and uaGate are affected by a NULL pointer dereference vulnerability.
A crafted HTTP packet with a missing HTTP URI can create a denial-of-service condition in Softing Secure Integration Server.
A crafted HTTP packet without a content-type header can create a denial-of-service condition in Softing Secure Integration Server.
A crafted HTTP packet with a -1 content-length header can create a denial-of-service condition in Softing Secure Integration Server.
- CRITICAL INFRASTRUCTURE SECTORS: Multiple sectors
- COUNTRIES/AREAS DEPLOYED: Worldwide
- COMPANY HEADQUARTERS LOCATION: Germany
Pedro Ribeiro and Radek Domanski, working with Trend Micro Zero Day Initiative, reported these vulnerabilities to Softing and CISA.
Softing released new versions to address these vulnerabilities and notified known users of the releases. Users are advised to update to the new versions:
- Softing Secure Integration Server V1.30
The latest software packages can be downloaded from the Softing website.
Softing recommends the following mitigations and workarounds:
- Change the admin password or create a new user with administrative rights and delete the default admin user.
- Configure the Windows firewall to block network requests to IP port 9000.
- Disable the HTTP Server in NGINX configuration of the Softing Secure Integration Server, only using the HTTPS server.
CISA recommends users take defensive measures to minimize the risk of exploitation of this vulnerability these vulnerabilities. Specifically, users should:
- Minimize network exposure for all control system devices and/or systems, and ensure they are not accessible from the Internet.
- Locate control system networks and remote devices behind firewalls and isolate them from business networks.
- 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.
CISA reminds organizations to perform proper impact analysis and risk assessment prior to deploying defensive measures.
No known public exploits specifically target these vulnerabilities. These vulnerabilities are exploitable remotely. These vulnerabilities have a low attack complexity.