Publication Date: |
|
Last Update: |
|
Current Version: | V1.5 |
CVSS v3.1 Base Score: | 8.2 |
Affected Product and Versions | Remediation |
---|---|
All versions |
|
All versions |
|
All versions |
|
All versions |
|
All versions < V7.0.3 |
|
All versions < V7.0.3 |
|
All versions |
|
All versions |
|
All versions < V7.0.3 |
|
All versions |
|
All versions < V7.0.3 |
|
All versions |
|
All versions < V7.0.3 |
|
All versions |
|
All versions < V6.0.9 |
Update to V6.0.9 or later version
|
All versions |
|
All versions < V8.2.1 |
Update to V8.2.1 or later version
Activate Field Interface Security in PCS 7 V9.0, and use a SIMATIC/SIPLUS CP443-1 Adv. to communicate with ES/OS
|
All versions < V7.0.3 |
|
All versions < V7.0.3 |
|
All versions |
|
All versions |
|
Siemens has identified the following specific workarounds and mitigations that customers can apply to reduce the risk:
Product-specific remediations or mitigations can be found in the section
Affected Products and Solution.
Please follow the General Security Recommendations.
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/.
Specially crafted packets sent to port 102/tcp via Ethernet interface, via PROFIBUS, or via Multi Point Interfaces (MPI) could cause the affected devices to go into defect mode. Manual reboot is required to resume normal operation.
Successful exploitation requires an attacker to be able to send specially crafted packets to port 102/tcp via Ethernet interface, via PROFIBUS or Multi Point Interfaces (MPI). No user interaction and no user privileges are required to exploit the security vulnerability. The vulnerability could allow causing a denial of service condition of the core functionality of the CPU, compromising the availability of the system.
CVSS v3.1 Base Score | 7.5 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C |
CWE | CWE-20: Improper Input Validation |
Sending of specially crafted packets to port 102/tcp via Ethernet interface via PROFIBUS or Multi Point Interfaces (MPI) could cause a denial of service condition on affected devices. Flashing with a firmware image may be required to recover the CPU.
Successful exploitation requires an attacker to have network access to port 102/tcp via Ethernet interface or to be able to send messages via PROFIBUS or Multi Point Interfaces (MPI) to the device. No user interaction is required. If no access protection is configured, no privileges are required to exploit the security vulnerability. The vulnerability could allow causing a denial of service condition of the core functionality of the CPU, compromising the availability of the system.
CVSS v3.1 Base Score | 8.2 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H/E:P/RL:O/RC:C |
CWE | CWE-347: Improper Verification of Cryptographic Signature |
V1.0 (2018-11-13): | Publication Date |
V1.1 (2019-05-14): | Updated acknowledgements and added solution for S7-400H V6 |
V1.2 (2020-02-10): | SIPLUS devices now explicitly mentioned in the list of affected products |
V1.3 (2022-08-09): | No fix planned for SIMATIC S7-400 PN/DP V6 and below CPU family, and for SIMATIC S7-400 H V4.5 and below CPU family |
V1.4 (2023-01-10): | No fix planned for SIMATIC S7-400 PN/DP V7 CPU family (incl. SIPLUS variants) |
V1.5 (2023-05-09): | Expanded SIMATIC S7-400 V7 CPU family (incl. SIPLUS variants) to individual products and MLFBs; added fix for SIMATIC S7-400 PN/DP V7 CPUs; clarified that no fix is planned for other S7-400 V7 CPUs |