Publication Date: |
|
Last Update: |
|
Current Version: | V1.4 |
CVSS v3.1 Base Score: | 5.3 |
Affected Product and Versions | Remediation |
---|---|
All versions only affected by CVE-2019-10943 |
|
All versions < V20.8 |
Update to V20.8 or later version
|
All versions >= V20.8 only affected by CVE-2019-10943 |
|
All versions |
|
All versions < V4.4.0 |
Update to V4.4.0 or later version
|
All versions >= V4.4.0 only affected by CVE-2019-10943 |
|
All versions < V2.8.1 |
Update to V2.8.1 or later version
|
All versions >= V2.8.1 only affected by CVE-2019-10943 |
|
All versions < V20.8 |
Update to V20.8 or later version
|
All versions >= V20.8 only affected by CVE-2019-10943 |
|
All versions < V3.0 |
Update to V3.0 or later version
|
All versions >= V3.0 only affected by CVE-2019-10943 |
|
Siemens has identified the following specific workarounds and mitigations that customers can apply to reduce the risk:
As a general security measure, Siemens strongly recommends to protect network access to devices with appropriate mechanisms. In order to operate the devices in a protected IT environment, Siemens recommends to configure the environment according to Siemens' operational guidelines for Industrial Security (Download: https://www.siemens.com/cert/operational-guidelines-industrial-security), and to follow the recommendations in the product manuals.
Additional information on Industrial Security by Siemens can be found at: https://www.siemens.com/industrialsecurity
The vulnerability classification has been performed by using the CVSS scoring system in version 3.1 (CVSS v3.1) (https://www.first.org/cvss/). The CVSS environmental score is specific to the customer’s environment and will impact the overall CVSS score. The environmental score should therefore be individually defined by the customer to accomplish final scoring.
An additional classification has been performed using the CWE classification, a community-developed list of common software security weaknesses. This serves as a common language and as a baseline for weakness identification, mitigation, and prevention efforts. A detailed list of CWE classes can be found at: https://cwe.mitre.org/.
Affected devices contain a message protection bypass vulnerability due to certain properties in the calculation used for integrity protection.
This could allow an attacker in a Man-in-the-Middle position to modify network traffic sent on port 102/tcp to the affected devices.
CVSS v3.1 Base Score | 3.7 |
CVSS Vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:U/RL:O/RC:C |
CWE | CWE-327: Use of a Broken or Risky Cryptographic Algorithm |
An attacker with network access to port 102/tcp could potentially modify the user program on the PLC in a way that the running code is different from the source code which is stored on the device.
An attacker must have network access to affected devices and must be able to perform changes to the user program. The vulnerability could impact the perceived integrity of the user program stored on the CPU. An engineer that tries to obtain the code of the user program running on the device, can receive different source code that is not actually running on the device.
CVSS v3.1 Base Score | 5.3 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:P/RL:T/RC:C |
CWE | CWE-353: Missing Support for Integrity Check |
V1.0 (2019-08-13): | Publication Date |
V1.1 (2019-12-10): | Added solution for CVE-2019-10929 for S7-1200 and S7-1500. SIPLUS devices now explicitly mentioned in the list of affected products |
V1.2 (2020-03-10): | Removed exclusion of SIMATIC S7-1500 CPU 1518-4 PN/DP. Added solution for CVE-2019-10929 for ET200SP CPU 1515SP PC2 and SIMATIC S7-1500 Software Controller |
V1.3 (2020-03-12): | Fix information about affected versions in product list. |
V1.4 (2022-08-09): | Added SIMATIC Drive Controller and SIMATIC ET 200SP Open Controller CPU 1515SP PC as affected products; separate fix information for the different CVE IDs; updated fix release URL for SIMATIC S7-1200; reviewed mitigation measure |