Skip to main content
VulnerabilityPublished Updated

CVE-2024-5717: 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, 15:59 UTC

CVSS 3.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.9% chance of exploitation in 30 days – higher than 87% 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 restrict network access to the Logsign Unified SecOps Platform HTTP API to trusted management networks only, using firewalls or network segmentation.
  2. Implement strong multi-factor authentication and monitor for suspicious authentication bypass attempts.
  3. Regularly audit and monitor logs for unusual command execution or API usage patterns indicative of exploitation attempts.
  4. Apply principle of least privilege to the service account running the Logsign platform, if possible, to limit root-level execution scope.
  5. Coordinate with Logsign vendor for official patches or updates addressing CVE-2024-5717 and apply them promptly once available.
  6. Until patches are available, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block command injection patterns targeting the HTTP API.
  7. Conduct internal penetration testing and vulnerability assessments focusing on the Logsign platform to identify potential exploitation paths.
  8. Maintain an incident response plan tailored to potential compromise of security monitoring infrastructure to ensure rapid containment and recovery.

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-24165.

References

Community reviews

Loading reviews…