Publication Date: |
|
Last Update: |
|
Current Version: | V1.6 |
CVSS v3.1 Base Score: | 9.6 |
Affected Product and Versions | Remediation |
---|---|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
|
|
|
|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
All versions |
Currently no fix is planned
|
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
Known Affected Products.
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 | 9.6 |
CVSS v3.1 Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:H/E:P/RL:T/RC:C |
CWE | CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') |
A timing attack, in a third-party component, could make the retrieval of the private key possible, used for encryption of sensitive data.
If a threat actor were to exploit this, the data integrity and security could be compromised.
CVSS v3.1 Base Score | 7.5 |
CVSS v3.1 Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:P/RL:O/RC:C |
CWE | CWE-208: Observable Timing Discrepancy |
A new variant of the POODLE attack has left a third-party component vulnerable due to the implementation flaws of the CBC encryption mode in TLS 1.0 to 1.2.
If an attacker were to exploit this, they could act as a man-in-the-middle and eavesdrop on encrypted communications.
CVSS v3.1 Base Score | 5.9 |
CVSS v3.1 Vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:P/RL:O/RC:C |
CWE | CWE-358: Improperly Implemented Security Check for Standard |
Within a third-party component, whenever memory allocation is requested, the out of bound size is not checked.
Therefore, if size exceeding the expected allocation is assigned, it could allocate a smaller buffer instead. If an attacker were to exploit this, they could cause a heap overflow.
CVSS v3.1 Base Score | 5.9 |
CVSS v3.1 Vector | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H/E:P/RL:O/RC:C |
CWE | CWE-122: Heap-based Buffer Overflow |
Within a third-party component, the process to allocate partition size fails to check memory boundaries.
Therefore, if a large amount is requested by an attacker, due to an integer-wrap around, it could result in a small size being allocated instead.
CVSS v3.1 Base Score | 5.9 |
CVSS v3.1 Vector | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H/E:P/RL:O/RC:C |
CWE | CWE-190: Integer Overflow or Wraparound |
The third-party component, in its TFTP functionality fails to check for null terminations in file names.
If an attacker were to exploit this, it could result in data corruption, and possibly a hard-fault of the application.
CVSS v3.1 Base Score | 7.5 |
CVSS v3.1 Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C |
CWE | CWE-754: Improper Check for Unusual or Exceptional Conditions |
On FIPS devices, if the TFTP feature is turned on, it is no longer considered to be in FIPS mode and considered as regular ROS device (described in FIPS user manual)
V1.0 (2022-03-08): | Publication Date |
V1.1 (2022-03-11): | Corrected the list of affected products and fix releases |
V1.2 (2022-04-12): | Added acknowledgements |
V1.3 (2023-03-14): | Corrected the list of affected products and added fix for V4.3.8 |
V1.4 (2023-04-11): | Added multiple missing affected products (only affected by CVE-2021-37208, CVE-2021-42016, CVE-2021-42017, CVE-2021-42018 and CVE-2021-42019) with no fix currently planned |
V1.5 (2023-12-12): | Added missing affected products: RUGGEDCOM RS416NCv2 V4.X, RUGGEDCOM RS416PNCv2 V4.x, RUGGEDCOM RS416v2 V4.X, RUGGEDCOM RS416Pv2 V4.X. Adjusted the name of RUGGEDCOM RS416NCv2 V5.X, RUGGEDCOM RS416PNCv2 V5.x, RUGGEDCOM RS416v2 V5.X, RUGGEDCOM RS416Pv2 V5.X (added reference to V5.X). Added Additional note for FIPS devices |
V1.6 (2025-08-12): | Added RUGGEDCOM RSG2100P (32M) and RUGGEDCOM RSG2100PNC (32M) for V4.x and V5.x |