Siemens SIPROTEC 5 Using DIGSI5 Protocol
Siemens SIPROTEC 5 vulnerable to arbitrary file uploads via DIGSI 5 protocol.
Siemens SIPROTEC 5 devices are vulnerable to arbitrary file uploads through the DIGSI 5 protocol, allowing authenticated attackers to upload malicious configuration files. This could lead to a denial of service or potentially code execution. Siemens has released updated versions with an allow-list feature to mitigate this risk and recommends specific countermeasures for devices where fixes are not yet available.
AI summary of the linked source. Not reviewed by an editor. How this works
Run Siemens?
Get an email when a new story names Siemens, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonSiemens SIPROTEC 5 devices contain a critical vulnerability that allows authenticated attackers to upload arbitrary, potentially malicious configuration files through the DIGSI 5 protocol, which could result in denial of service or remote code execution. The root cause is an insufficient file validation mechanism — the protocol lacked an allow-list to restrict what types of configuration files could be uploaded. This is especially concerning in operational technology (OT) and industrial control system (ICS) environments, where availability and integrity are mission-critical. Even authenticated users should not have unconstrained ability to upload arbitrary files to safety-critical devices, illustrating why least-privilege and input validation must be enforced at the protocol level.
What helps against this
How we list vendors- Automated patch management
Known holes get closed in days, not months.
- Network segmentation and microsegmentation
One compromised machine can no longer reach everything else.
- OT and industrial control system security
Factory, building and utility control systems get visibility and protection.
Indicators of Compromise
Extracted by AI from the linked source. Not reviewed by an editor. How this works
- cve — CVE-2025-40808