Publication Date: |
|
Last Update: |
|
Current Version: | V1.4 |
CVSS v3.1 Base Score: | 4.6 |
Affected Product and Versions | Remediation |
---|---|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
All versions affected by CVE-2022-38773 |
Currently no fix is planned
|
Siemens has identified the following specific workarounds and mitigations that customers can apply to reduce the risk:
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
This chapter describes all vulnerabilities (CVE-IDs) addressed in this security advisory. Wherever applicable, it also documents the product-specific impact of the individual vulnerabilities.
CVSS v3.1 Base Score | 4.6 |
CVSS v3.1 Vector | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N/E:P/RL:T/RC:C |
CWE | CWE-1326: Missing Immutable Root of Trust in Hardware |
Siemens has released the following new hardware versions of the S7-1500 product family. They contain a new secure boot mechanism that resolves the vulnerability:
Siemens is working on new hardware versions for additional PLC types to address this vulnerability further.
For more information please also refer to the related product support article: https://support.industry.siemens.com/cs/ww/en/view/109816536/.
V1.0 (2023-01-10): | Publication Date |
V1.1 (2023-02-14): | Added information about additional new S7-1500 hardware versions and a reference to the related product support title |
V1.2 (2023-03-14): | Added information about additional new S7-1500 hardware versions: SIMATIC S7-1500 CPU 1514SP( F)-2 PN |
V1.3 (2023-12-12): | Added information about additional new S7-1500 hardware versions: SIMATIC S7-1500 CPU 1513pro( F)-2 PN, SIMATIC S7-1500 CPU 1516pro( F)-2 PN |
V1.4 (2024-06-11): | Added information about additional new S7-1500 hardware versions: SIMATIC S7-1500 CPU 1511C-1 PN, SIMATIC S7-1500 CPU 1512C-1 PN |