CVE-2024-5718

8.1 HIGH

📋 TL;DR

CVE-2024-5718 is an unauthenticated remote code execution vulnerability in Logsign Unified SecOps Platform's cluster HTTP API. Attackers can execute arbitrary code as root without authentication, affecting all deployments with the vulnerable API enabled. Organizations using Logsign Unified SecOps Platform are at risk.

💻 Affected Systems

Products:
  • Logsign Unified SecOps Platform
Versions: Versions prior to 6.4.8
Operating Systems: Linux-based systems where Logsign is deployed
Default Config Vulnerable: ⚠️ Yes
Notes: The cluster HTTP API must be enabled (listens on TCP port 1924 by default when enabled).

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise with root-level access, data exfiltration, ransomware deployment, and persistent backdoor installation.

🟠

Likely Case

Initial foothold leading to lateral movement within the network, credential harvesting, and deployment of additional malware.

🟢

If Mitigated

Limited impact if proper network segmentation and access controls prevent exploitation attempts.

🌐 Internet-Facing: HIGH - The vulnerable service listens on TCP port 1924 and requires no authentication, making internet-facing instances extremely vulnerable.
🏢 Internal Only: HIGH - Even internally, the lack of authentication makes this easily exploitable by any internal threat actor or compromised host.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

No authentication required and the vulnerability is in a network-accessible API, making exploitation straightforward for attackers with network access.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 6.4.8

Vendor Advisory: https://support.logsign.net/hc/en-us/articles/19316621924754-03-06-2024-Version-6-4-8-Release-Notes

Restart Required: Yes

Instructions:

1. Backup current configuration and data. 2. Download Logsign Unified SecOps Platform version 6.4.8 from official sources. 3. Follow vendor upgrade instructions to apply the patch. 4. Restart the Logsign service. 5. Verify the update was successful.

🔧 Temporary Workarounds

Disable Cluster HTTP API

linux

Disable the vulnerable cluster HTTP API if not required for operations

Consult Logsign documentation for disabling the cluster API service

Network Access Control

linux

Restrict access to TCP port 1924 using firewall rules

iptables -A INPUT -p tcp --dport 1924 -j DROP
ufw deny 1924/tcp

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate Logsign systems from untrusted networks
  • Deploy intrusion detection/prevention systems to monitor and block exploitation attempts on port 1924

🔍 How to Verify

Check if Vulnerable:

Check if Logsign version is below 6.4.8 and if TCP port 1924 is listening and accessible

Check Version:

Check Logsign web interface or configuration files for version information

Verify Fix Applied:

Verify Logsign version is 6.4.8 or higher and test that unauthorized access to the cluster API is blocked

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to cluster API endpoints
  • Unusual process execution from Logsign services
  • Failed authentication attempts to port 1924

Network Indicators:

  • Unusual traffic to TCP port 1924 from unexpected sources
  • HTTP requests to cluster API without authentication headers

SIEM Query:

source_port:1924 AND (http_method:POST OR http_method:PUT) AND NOT user_agent:"Logsign"

🔗 References

📤 Share & Export