Secure Boot alteration via unprotected EFI variables
Published Mar 11, 2025 · Updated Sep 8, 2026
Protection mechanism failure in Siemens SIMATIC devices allows local users to alter Secure Boot configuration through EFI variables. The firmware does not adequately protect stored EFI variables, allowing direct flash-controller communication to change Secure Boot settings without firmware authorization. Exploitation requires root or administrator access on the device and can undermine the boot trust boundary across the affected hardware.
Summary
What happened
Protection mechanism failure in Siemens SIMATIC devices allows local users to alter Secure Boot configuration through EFI variables. The firmware does not adequately protect stored EFI variables, allowing direct flash-controller communication to change Secure Boot settings without firmware authorization. Exploitation requires root or administrator access on the device and can undermine the boot trust boundary across the affected hardware.
The record
- CVE
- CVE-2024-56181
- Published
- Mar 11, 2025
- Updated
- Sep 8, 2026
- Vendor
- Siemens
- Product
- SIMATIC IPC477E PRO
- Classifications
- CWE-693, T1562.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 11, 2025CVE publishedPublication date reported by the CVE source.
- Sep 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <V21.01.21
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo