Publication Date:
Last Update:
Current Version: V1.2
CVSS v3.1 Base Score: 9.9
Affected Product and Versions Remediation

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10

All versions < V3.10
  • Do not access links from untrusted sources while logged in at SICAM P850 or SICAM P855 devices

Product-specific remediations or mitigations can be found in the section Affected Products and Solution.
Please follow the General Security Recommendations.

Operators of critical power systems (e.g. TSOs or DSOs) worldwide are usually required by regulations to build resilience into the power grids by applying multi-level redundant secondary protection schemes. It is therefore recommended that the operators check whether appropriate resilient protection measures are in place. The risk of cyber incidents impacting the grid's reliability can thus be minimized by virtue of the grid design. Siemens strongly recommends applying the provided security updates using the corresponding tooling and documented procedures made available with the product. If supported by the product, an automated means to apply the security updates across multiple product instances may be used. Siemens strongly recommends prior validation of any security update before being applied, and supervision by trained staff of the update process in the target environment. As a general security measure Siemens strongly recommends to protect network access with appropriate mechanisms (e.g. firewalls, segmentation, VPN). It is advised to configure the environment according to our operational guidelines in order to run the devices in a protected IT environment.

Recommended security guidelines can be found at: https://www.siemens.com/gridsecurity

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.5
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
CWE CWE-384: Session Fixation
CVSS v3.1 Base Score 9.8
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
CWE CWE-141: Improper Neutralization of Parameter/Argument Delimiters
CVSS v3.1 Base Score 9.9
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C
CWE CWE-20: Improper Input Validation
CVSS v3.1 Base Score 9.9
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C
CWE CWE-20: Improper Input Validation
CVSS v3.1 Base Score 9.9
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C
CWE CWE-20: Improper Input Validation

  • Michael Messner from Siemens Energy for reporting the vulnerabilities

https://www.siemens.com/cert/advisories

V1.0 (2022-10-11): Publication Date
V1.1 (2022-12-13): Corrected description for CVE-2022-41665; corrected CVSS score for CVE-2022-40226
V1.2 (2023-06-13): Added CVE-2022-43439, CVE-2022-43545 and CVE-2022-43546