Skip to main content
VulnerabilityPublished Updated

CVE-2024-5720: Logsign Unified SecOps Platform · OS Command Injection

Affects Logsign Unified SecOps PlatformSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.6% chance of exploitation in 30 days – higher than 85% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Logsign Unified SecOps PlatformAffected
  • =6.4.6
Fixed in–

AI-suggested

  1. Immediately apply any available patches or updates from Logsign addressing this vulnerability once released.
  2. If patches are not yet available, restrict access to the Logsign Unified SecOps Platform HTTP API to trusted networks only, using network segmentation and firewall rules.
  3. Implement strict input validation and sanitization on all user inputs interacting with the platform, especially those that may be passed to system commands.
  4. Employ multi-factor authentication and monitor authentication logs closely to detect potential bypass attempts.
  5. Use application-layer firewalls or web application firewalls (WAFs) to detect and block suspicious command injection patterns targeting the HTTP API.
  6. Regularly audit and monitor system and application logs for unusual activities indicative of exploitation attempts.
  7. Limit the privileges of the service account running the platform where possible to reduce the impact of a successful exploit.
  8. Conduct penetration testing and code reviews focused on input validation and authentication mechanisms to identify similar weaknesses.
  9. Prepare incident response plans specifically for potential exploitation of this vulnerability to enable rapid containment and remediation.

Description

Logsign Unified SecOps Platform Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Logsign Unified SecOps Platform. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the implementation of the HTTP API. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-24168.

References

Community reviews

Loading reviews…