CVE-2024-5721: Logsign Unified SecOps Platform · Missing Authentication
Affects Logsign Unified SecOps PlatformSource CVE Database V5
Not known to be exploited · public exploit available (Metasploit) · CVSS 8.1 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 5.9% chance of exploitation in 30 days – higher than 93% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| Logsign Unified SecOps Platform | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2024-5721 effectively, organizations should take the following specific actions: 1) Immediately restrict network access to TCP port 1924 on all Logsign Unified SecOps Platform installations, limiting it to trusted management networks or disabling the cluster HTTP API if not required. 2) Implement network-level controls such as firewall rules and segmentation to prevent unauthorized external access to the vulnerable interface. 3) Monitor network traffic and logs for any unusual or unauthorized access attempts targeting port 1924. 4) Coordinate with Logsign for timely updates and patches; apply vendor-provided fixes as soon as they become available. 5) Conduct a thorough security review of the platform's deployment, ensuring that default configurations do not expose critical interfaces unnecessarily. 6) Employ intrusion detection and prevention systems to detect exploitation attempts. 7) Prepare incident response plans specific to potential compromise of the SecOps platform, including forensic readiness and recovery procedures. 8) Educate security teams about the vulnerability and ensure they are vigilant for signs of exploitation. These measures go beyond generic advice by focusing on network isolation, proactive monitoring, and operational readiness tailored to the unique risks posed by this vulnerability.
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 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-24169.