Publication Date:
Last Update:
Current Version: V1.4
CVSS v3.1 Base Score: 4.6
Un-/Collapse All
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
  • Restrict physical access to affected devices to trusted personnel to avoid hardware tampering (e.g., place the devices in locked control cabinets)

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

Un-/Collapse All

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

  • Yuanzhe Wu and Ang Cui from Red Balloon Security for coordinated disclosure

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:

  • SIMATIC S7-1500 CPU 1510SP F-1 PN (6ES7510-1SK03-0AB0)
  • SIMATIC S7-1500 CPU 1510SP-1 PN (6ES7510-1DK03-0AB0)
  • SIMATIC S7-1500 CPU 1511-1 PN (6ES7511-1AL03-0AB0)
  • SIMATIC S7-1500 CPU 1511C-1 PN (6ES7511-1CL03-0AB0)
  • SIMATIC S7-1500 CPU 1511F-1 PN (6ES7511-1FL03-0AB0)
  • SIMATIC S7-1500 CPU 1511T-1 PN (6ES7511-1TL03-0AB0)
  • SIMATIC S7-1500 CPU 1511TF-1 PN (6ES7511-1UL03-0AB0)
  • SIMATIC S7-1500 CPU 1512C-1 PN (6ES7512-1CM03-0AB0)
  • SIMATIC S7-1500 CPU 1512SP F-1 PN (6ES7512-1SM03-0AB0)
  • SIMATIC S7-1500 CPU 1512SP-1 PN (6ES7512-1DM03-0AB0)
  • SIMATIC S7-1500 CPU 1513-1 PN (6ES7513-1AM03-0AB0)
  • SIMATIC S7-1500 CPU 1513F-1 PN (6ES7513-1FM03-0AB0)
  • SIMATIC S7-1500 CPU 1513R-1 PN (6ES7513-1RM03-0AB0)
  • SIMATIC S7-1500 CPU 1513pro-2 PN (6ES7513-2PM03-0AB0)
  • SIMATIC S7-1500 CPU 1513pro F-2 PN (6ES7513-2GM03-0AB0)
  • SIMATIC S7-1500 CPU 1514SP F-2 PN (6ES7514-2SN03-0AB0)
  • SIMATIC S7-1500 CPU 1514SP-2 PN (6ES7514-2DN03-0AB0)
  • SIMATIC S7-1500 CPU 1515-2 PN (6ES7515-2AN03-0AB0)
  • SIMATIC S7-1500 CPU 1515F-2 PN (6ES7515-2FN03-0AB0)
  • SIMATIC S7-1500 CPU 1515R-2 PN (6ES7515-2RN03-0AB0)
  • SIMATIC S7-1500 CPU 1515T-2 PN (6ES7515-2TN03-0AB0)
  • SIMATIC S7-1500 CPU 1515TF-2 PN (6ES7515-2UN03-0AB0)
  • SIMATIC S7-1500 CPU 1516-3 PN/DP (6ES7516-3AP03-0AB0)
  • SIMATIC S7-1500 CPU 1516F-3 PN/DP (6ES7516-3FP03-0AB0)
  • SIMATIC S7-1500 CPU 1516pro-2 PN (6ES7516-2PP03-0AB0)
  • SIMATIC S7-1500 CPU 1516pro F-2 PN (6ES7516-2GP03-0AB0)

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/.

https://www.siemens.com/cert/advisories
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