Unauthenticated code execution via SCPI command injection
Published Jun 14, 2023 · Updated Jan 3, 2025
Command injection in Siglent SDS1xx4X-E firmware 6.1.37R9.ADS allows remote attackers to execute arbitrary code through SCPI. The SYST:COMM:LAN:IPAD handler passes its address argument to system(), allowing shell separators in untrusted SCPI input to chain commands. No authentication is required on either SCPI port or the web endpoint, so network access permits commands with the embedded system's privileges.
Summary
What happened
Command injection in Siglent SDS1xx4X-E firmware 6.1.37R9.ADS allows remote attackers to execute arbitrary code through SCPI. The SYST:COMM:LAN:IPAD handler passes its address argument to system(), allowing shell separators in untrusted SCPI input to chain commands. No authentication is required on either SCPI port or the web endpoint, so network access permits commands with the embedded system's privileges.
The record
- CVE
- CVE-2023-25367
- Published
- Jun 14, 2023
- Updated
- Jan 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 14, 2023CVE publishedPublication date reported by the CVE source.
- Jan 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- SDS1xx4X-E SCPI command-injection proof of conceptproof of concept · demonstrated
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