Publication Date: |
|
Last Update: |
|
Current Version: | V1.0 |
CVSS v3.1 Base Score: | 7.8 |
CVSS v4.0 Base Score: | 8.5 |
Affected Product and Versions | Remediation |
---|---|
|
|
All versions affected by CVE-2025-30033 |
Currently no fix is planned
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is planned
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
|
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
|
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
|
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
|
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
|
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
|
|
|
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
|
|
|
|
|
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
|
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
|
|
|
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is planned
|
|
|
|
|
|
|
|
|
|
|
All versions < V4.0.1 affected by CVE-2025-30033 |
Update to V4.0.1 or later version
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
|
|
All versions < V7.0 Update 1 affected by CVE-2025-30033 |
Update to V7.0 Update 1 or later version
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
|
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
|
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions < V4.0 affected by CVE-2025-30033 |
Update to V4.0 or later version
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions < V3.1.2.2 affected by CVE-2025-30033 |
Update to V3.1.2.2 or later version
|
All versions < V3.0.6 affected by CVE-2025-30033 |
Update to V3.0.6 or later version
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
|
|
All versions affected by CVE-2025-30033 |
Currently no fix is available
|
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 | 7.8 |
CVSS v3.1 Vector | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
CVSS v4.0 Base Score | 8.5 |
CVSS v4.0 Vector | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
CWE | CWE-427: Uncontrolled Search Path Element |
Siemens uses an internal software component to bundle Siemens software into self-contained installer executables. This component, called "Siemens Web Installer Application (SIWA)", which is vulnerable to DLL hijacking. To ensure no untrusted DLL files are in the setup directory, install applications only from a directory containing only the installer file. This minimizes the likelihood of malicious DLLs being present.
V1.0 (2025-08-12): | Publication Date |