Publication Date: |
|
Last Update: |
|
Current Version: | V1.1 |
CVSS v3.1 Base Score: | 7.8 |
Affected Product and Versions | Remediation |
---|---|
All versions < VX.2.10 Update 13 |
|
All versions < VX.2.11 Update 11 |
|
All versions < VX.2.12 Update 5 |
|
All versions < VX.2.13 Update 1 |
|
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/.
CVSS v3.1 Base Score | 7.8 |
CVSS Vector | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C |
CWE | CWE-732: Incorrect Permission Assignment for Critical Resource |
The previous update does not fully fix the vulnerability in versions prior or equal to VX.2.11. A new fix is then provided for VX.2.11 and also VX.2.10.
V1.0 (2022-06-14): | Publication Date |
V1.1 (2023-06-13): | Added new fix for versions VX.2.10 and VX.2.11. Added VX.2.12 and VX.2.13 as affected versions |