Siemens SINEC INS
1. EXECUTIVE SUMMARY
- CVSS v3 8.8
- ATTENTION: Exploitable remotely/Low attack complexity
- Vendor: Siemens
- Equipment: SINEC INS
- Vulnerabilities: Improper Input Validation, Integer Overflow or Wraparound, Uncontrolled Resource Consumption, Command Injection, Inadequate Encryption Strength, Missing Encryption of Sensitive Data, Improper Restriction of Operations Within the Bounds of a Memory Buffer, Exposure of Private Personal Information to an Unauthorized Actor, Open Redirect, Improper Resource Shutdown or Release, Server-Side Request Forgery (SSRF)
2. RISK EVALUATION
Successful exploitation of these vulnerabilities could allow an attacker to cause a denial-of-service condition, disclose sensitive data, or violate the system integrity.
3. TECHNICAL DETAILS
3.1 AFFECTED PRODUCTS
The following versions of Siemens SINEC INS, a software tool for central network services, are affected:
- Siemens SINEC INS: All versions prior to V1.0 SP2
3.2 VULNERABILITY OVERVIEW
The UAParser.js package, versions prior to 0.7.23, are vulnerable to regular expression denial-of-service in multiple RegExes.
The JSON-C application programming interface (API) documentation through version 0.14 has an integer overflow and out-of-bounds write via a large JSON file.
The Axios NPM package, version 0.21.0, contains an SSRF vulnerability that could allow an attacker to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address.
Lodash versions prior to 4.17.21 are vulnerable to regular expression denial-of-service via the toNumber, trim, and trimEnd functions.
Axios is vulnerable to inefficient regular expression complexity.
TLS 1.3 default curves are impacted by EC algorithms affected by a carry propagation bug in the MIPS32 and MIPS64 squaring procedure.
Lodash versions prior to 4.17.21 are vulnerable to command injection via the template function.
OpenSSL 1.0.2 servers from version 1.0.2s to 1.0.2x are affected by inverted logic regarding padding checks. Implementation of this padding check inverted the logic so that the connection attempt is accepted if the padding is present and rejected if it is absent. Resultantly, a server will accept a connection if a version rollback attack has occurred, and the server will erroneously reject a connection if a normal SSLv2 connection attempt is made
Upon attempting to create a unique hash value based on the issuer and serial number data contained within an X509 certificate, the OpenSSL public API function “X509_issuer_and_serial_hash()”fails to correctly handle any errors that may occur while parsing the issuer field. This may result in a NULL pointer deref and a crash leading to a denial-of-service condition.
The following versions of BIND, 9.11.0 -> 9.11.36 9.12.0 -> 9.16.26 9.17.0 -> 9.18.0, the following versions of BIND Supported Preview Editions, 9.11.4-S1 -> 9.11.36-S1 9.16.8-S1 -> 9.16.26-S1, and versions of BIND 9 –prior to 9.1.0, including Supported Preview Editions, are potentially vulnerable. However, these versions have not been tested as they are EOL. An attacker could contaminate the cache with incorrect records, resulting in queries being made to the wrong servers and false information being.
The affected products contain the third-party component, ISC DHCP. This component introduces a vulnerability when used as a DHCP client or server when storing and reading DHCP lease information. An attacker could exploit this vulnerability to affect the availability of the DHCP client, availability of the server, or the confidentiality of the data. Other potential exploits include impacts to the integrity of the device through a buffer overflow or a remote-code execution.
The follow-redirect could potentially expose private personal information to an attacker.
The node-fetch could potentially expose sensitive information to an attacker.
The following versions of BIND, 9.16.11 -> 9.16.26, 9.17.0 -> 9.18.0, and the following versions of BIND Supported Preview Edition, 9.16.11-S1 -> 9.16.26-S1, are affected. Specifically crafted TCP streams can suspend BIND connections in a CLOSE_WAIT status for an indefinite time, even after the client has terminated the connection.
- CRITICAL INFRASTRUCTURE SECTORS: Multiple
- COUNTRIES/AREAS DEPLOYED: Worldwide
- COMPANY HEADQUARTERS LOCATION: Germany
Siemens reported these vulnerabilities to CISA.
Siemens recommends updating to V1.0 SP2 or later.
As a general security measure, Siemens strongly recommends protecting network access to devices with appropriate mechanisms. In order to operate the devices in a protected IT environment, Siemens recommends configuring the environment according to Siemens’ operational guidelines for industrial security, and to follow the recommendations in the product manuals.
Additional information on industrial security by Siemens can be found here.
CISA recommends users take defensive measures to minimize the risk of exploitation of 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.
CISA also provides a section for control systems security recommended practices on the ICS webpage at cisa.gov/ics. Several CISA products detailing cyber defense best practices are available for reading and download, including Improving Industrial Control Systems Cybersecurity with Defense-in-Depth Strategies.
Additional mitigation guidance and recommended practices are publicly available on the ICS webpage at cisa.gov/ics in the technical information paper, ICS-TIP-12-146-01B--Targeted Cyber Intrusion Detection and Mitigation Strategies.
Organizations observing suspected malicious activity should follow established internal procedures and report findings to CISA for tracking and correlation against other incidents.
No known public exploits specifically target these vulnerabilities.