Root code execution via HTTP API command injection
Published Nov 22, 2024 · Updated Nov 26, 2024
Command injection in Logsign Unified SecOps Platform 6.4.6 through 6.4.7 allows remote attackers to execute code as root through its HTTP API. The HTTP API passes a user-supplied string to a system call without proper validation, allowing injected operating-system commands. An authenticated session is normally required, but the existing authentication mechanism can be bypassed, so successful exploitation grants root-level command execution.
Summary
What happened
Command injection in Logsign Unified SecOps Platform 6.4.6 through 6.4.7 allows remote attackers to execute code as root through its HTTP API. The HTTP API passes a user-supplied string to a system call without proper validation, allowing injected operating-system commands. An authenticated session is normally required, but the existing authentication mechanism can be bypassed, so successful exploitation grants root-level command execution.
The record
- CVE
- CVE-2024-5717
- Published
- Nov 22, 2024
- Updated
- Nov 26, 2024
- Vendor
- Logsign
- Product
- Logsign Unified SecOps Platform
- Classifications
- CWE-78, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 22, 2024CVE publishedPublication date reported by the CVE source.
- Nov 26, 2024Record 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=6.4.6
- Affected versionversion=6.4.6 <6.4.8
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