Physical command execution via unrestricted development shell
Published Feb 11, 2025 · Updated Nov 11, 2025
Improper debug-interface access in Siemens SIPROTEC 5 devices allows physically proximate attackers to execute arbitrary device commands. A development shell remains reachable through a physical interface because the device does not properly restrict access to that shell. No credentials are required, but direct physical access is necessary; successful exploitation grants command execution with device-wide confidentiality, integrity, and availability impact.
Summary
What happened
Improper debug-interface access in Siemens SIPROTEC 5 devices allows physically proximate attackers to execute arbitrary device commands. A development shell remains reachable through a physical interface because the device does not properly restrict access to that shell. No credentials are required, but direct physical access is necessary; successful exploitation grants command execution with device-wide confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2024-53648
- Published
- Feb 11, 2025
- Updated
- Nov 11, 2025
- Vendor
- Siemens
- Product
- SIPROTEC 5 7SA87 (CP200)
- Classifications
- CWE-489, T1059
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2025CVE publishedPublication date reported by the CVE source.
- Nov 11, 2025Record 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 <*
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.
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