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
PRODUCT DESCRIPTION
SCALANCE X switches are used to connect industrial components like Programmable Logic Controllers (PLCs) or Human Machine Interfaces (HMIs).
SIPLUS extreme products are designed for reliable operation under extreme conditions and are based on SIMATIC, LOGO!, SITOP, SINAMICS, SIMOTION, SCALANCE or other devices. SIPLUS devices use the same firmware as the product they are based on.
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.
Vulnerability CVE-2012-1802
The embedded web server on affected devices contains a buffer overflow vulnerability. This could allow remote attackers to cause a denial of service (device reboot) or possibly execute arbitrary code via a malformed URL.
CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
ACKNOWLEDGMENTS
Siemens thanks the following parties for their efforts:
Artem Zinenko from Kaspersky for pointing out that SIPLUS should also be mentioned
Jürgen Bilberger from Daimler TSS GmbH for coordinated disclosure
ADDITIONAL INFORMATION
For further inquiries on security vulnerabilities in Siemens products and solutions, please contact the Siemens ProductCERT:
https://www.siemens.com/cert/advisories
HISTORY DATA
V1.2 (2012-04-05):
Publication Date
V1.3 (2020-02-10):
SIPLUS devices now explicitly mentioned in the list of affected products
V1.4 (2026-02-10):
Used CVE ID (CVE-2012-1802) instead of the deprecated SVE ID (SVE-2012-0002); Corrected CVSS vector and added mitigation information; Updated SSA to current data model and support of csaf