The vulnerabilities are 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, and server-side request forgery (SSRF).
Successful exploitation of these remotely exploitable vulnerabilities, which Siemens self-reported, could allow an attacker to cause a denial-of-service condition, disclose sensitive data, or violate the system integrity.
The following versions of Siemens SINEC INS, a software tool for central network services, suffer from the vulnerabilities: All versions prior to V1.0 SP2.
In one issue, the UAParser.js package, versions prior to 0.7.23, are vulnerable to regular expression denial-of-service in multiple RegExes.
CVE-2020-7793 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.5.
In addition, 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.
CVE-2020-12762 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.8.
Also, 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.
CVE-2020-28168 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.9.
In another issue, Lodash versions prior to 4.17.21 are vulnerable to regular expression denial-of-service via the toNumber, trim, and trimEnd functions.
CVE-2020-28500 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.3.
In addition, Axios is vulnerable to inefficient regular expression complexity.
CVE-2021-3749 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.5.
Also, TLS 1.3 default curves are impacted by EC algorithms affected by a carry propagation bug in the MIPS32 and MIPS64 squaring procedure.
CVE-2021-4160 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.9.
In another issue, Lodash versions prior to 4.17.21 are vulnerable to command injection via the template function.
CVE-2021-23337 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 7.2.
In addition, 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.
CVE-2021-23839 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 3.7.
Also, 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.
CVE-2021-23841 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.9.
In another issue, 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.
CVE-2021-25220 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 8.6.
In addition, 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.
CVE-2021-25217 is the case number assigned to this vulnerability, which has as CVSS v3 base score of 8.8.
Also, the follow-redirect could potentially expose private personal information to an attacker.
CVE-2022-0155 is the case number assigned to this vulnerability, which has as CVSS v3 base score of 6.5.
In another issue, the node-fetch could potentially expose sensitive information to an attacker.
CVE-2022-0235 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 6.1.
In addition, 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.
CVE-2022-0396 is the case number assigned to this vulnerability, which has a CVSS v3 base score of 5.3.
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 these low complexity vulnerabilities.
Siemens recommends updating to V1.0 SP2 or later.
As a general security measure, Siemens 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.
Click here for additional information on industrial security by Siemens.