dbcve.org
Unified Secops PlatformApplication · Logsign

CVE-2024-5718

HIGH · 8.1 CVSS v3.1 Published 2024-11-22
Fix available
A fix is available. Upgrade to 6.4.8 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Missing authentication in Logsign Unified SecOps Platform's cluster HTTP API (TCP port 1924) allows unauthenticated remote attackers to execute arbitrary code as root. The vulnerability stems from the lack of authentication checks before granting access to sensitive API functionality.

MitigationRestrict network access to port 1924 via firewall rules or network segmentation until vendor authentication patch is applied; verify cluster API is disabled if not required in production environments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Unified Secops PlatformApplication
Affected:>= 6.4.6, < 6.4.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Logsign Unified SecOps Platform installation
    Check if Logsign is installed on the system by looking for common installation directories or running: ps aux | grep -i logsign or systemctl list-units | grep logsign
    Affected if Logsign Unified SecOps Platform is not installed on the system - no action needed
  2. Determine installed Logsign version
    Run: rpm -qa | grep logsign or check /opt/logsign/version 2>/dev/null if the product was installed using standard paths
    Affected if Installed version is 6.4.6, 6.4.7, or any 6.4.6.x/6.4.7.x release - version falls within affected range >= 6.4.6, < 6.4.8
  3. Verify if TCP port 1924 is listening
    Run: netstat -tlnp | grep 1924 or ss -tlnp | grep 1924 to check if the cluster HTTP API port is open and listening
    Affected if Port 1924 is open and listening - the vulnerable API endpoint is exposed
  4. Test API accessibility without authentication
    Run: curl -s http://localhost:1924/api/status or curl -s http://127.0.0.1:1924/api/cluster 2>/dev/null to check if the API responds without requiring credentials
    Affected if API returns any JSON response or cluster status information without authentication - the vulnerability is present and exploitable

A system is affected if Logsign Unified SecOps Platform version 6.4.6 through 6.4.7.x is installed AND TCP port 1924 is open with the cluster API responding without authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.4.8 or later
Fixed in 6.4.8
Interim mitigation

Restrict network access to port 1924 via firewall rules or network segmentation until vendor authentication patch is applied; verify cluster API is disabled if not required in production environments.

Recommended fix High confidence

Logsign Unified SecOps Platform 6.4.8 or later

  1. Backup the current Logsign Unified SecOps Platform installation and configuration
  2. Download Logsign Unified SecOps Platform version 6.4.8 or later from the official vendor support site (support.logsign.net)
  3. Follow the vendor's documented upgrade procedure to apply the update
  4. Verify the upgrade was successful by checking the version number
  5. Confirm the cluster HTTP API on TCP port 1924 is now properly requiring authentication
  6. Test that legitimate administrative functions still work correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Unified Secops Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5718 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5718 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data