Skip to main content
CVE-2024-5718VulnerabilityPublished Updated

CVE-2024-5718: Logsign Unified SecOps Platform · Missing Authentication

Affects Logsign Unified SecOps PlatformSource CVE Database V5

0

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 06:15 UTC

CVSS 3.0 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.4% chance of exploitation in 30 days – higher than 73% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:H/PR:N/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 2026-10-25.

What to do

Affected software

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

AI-suggested

Until an official patch is released, organizations should take immediate, specific actions to mitigate this vulnerability: 1) Disable the cluster HTTP API on TCP port 1924 if it is not strictly necessary for operations. 2) Restrict network access to the cluster API port using firewall rules or network segmentation, limiting access only to trusted internal hosts. 3) Implement strict access controls and monitoring on the network segment hosting the Logsign platform to detect any unauthorized connection attempts. 4) Employ host-based intrusion detection systems (HIDS) to monitor for suspicious activity or unexpected process execution on the Logsign server. 5) Regularly audit and review logs for signs of exploitation attempts. 6) Prepare incident response plans specifically for potential compromise of the SecOps platform. 7) Engage with Logsign support or vendor channels to obtain updates on patches or official remediation guidance. 8) Consider deploying network-level authentication proxies or VPNs to add an authentication layer around the cluster API if disabling it is not feasible. These targeted mitigations go beyond generic advice by focusing on isolating and controlling access to the vulnerable API and enhancing detection capabilities.

Description

Logsign Unified SecOps Platform Missing Authentication Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Logsign Unified SecOps Platform. Authentication is not required to exploit this vulnerability. The specific flaw exists within the implementation of the cluster HTTP API, which listens on TCP port 1924 by default when enabled. The issue results from the lack of authentication prior to allowing access to functionality. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-24166.

References

Community reviews

Loading reviews…