dbcve.org
Unified Secops PlatformApplication · Logsign

CVE-2024-5719

HIGH · 8.8 CVSS v3.0 Published 2024-11-22
Fix available
A fix is available. Upgrade to 6.4.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 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-24167.

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

Command injection vulnerability in Logsign Unified SecOps Platform's HTTP API allows remote attackers to execute arbitrary code as root. The flaw results from insufficient validation of user-supplied input before it is used in a system call. Additionally, the authentication mechanism can be bypassed, making exploitation achievable by remote attackers.

MitigationApply vendor-supplied patches for Logsign Unified SecOps Platform. Until patches are available, restrict network access to the API endpoint and monitor for suspicious command execution patterns.

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/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 if Logsign Unified SecOps Platform is installed
    Locate the Logsign installation directory or check for running Logsign services/processes on the system
    Affected if Logsign Unified SecOps Platform is present on the system
  2. Check the installed version of Logsign
    Access the Logsign web interface and navigate to the About or System Information section, or use the command line to retrieve the version if applicable
    Affected if The installed version is greater than or equal to 6.4.6 and less than 6.4.8
  3. Verify HTTP API accessibility
    Check if the Logsign HTTP API endpoint is exposed to network access, particularly untrusted networks. Review firewall rules and network configuration for the Logsign server.
    Affected if The HTTP API is accessible from untrusted networks or the internet
  4. Check for signs of exploitation or compromise
    Review Logsign API access logs and system audit logs for unusual or unauthorized command execution patterns, unexpected API calls, or anomalies in authentication behavior
    Affected if There is evidence of unauthorized API access, unexpected command execution, or authentication bypass attempts in logs

A system is affected if Logsign Unified SecOps Platform version 6.4.6 through 6.4.7 is installed and its HTTP API is accessible, regardless of authentication configuration, due to the authentication bypass combined with command injection.

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

Apply vendor-supplied patches for Logsign Unified SecOps Platform. Until patches are available, restrict network access to the API endpoint and monitor for suspicious command execution patterns.

Recommended fix Moderate confidence

Logsign Unified SecOps Platform 6.4.8

  1. 1. Backup the current Logsign Unified SecOps Platform configuration and data
  2. 2. Download Logsign Unified SecOps Platform version 6.4.8 or later from the official vendor portal at support.logsign.net
  3. 3. Review the upgrade documentation provided by Logsign
  4. 4. Perform the upgrade following the vendor's standard upgrade procedure
  5. 5. Verify the upgrade was successful by checking the version number in the system
  6. 6. Test that normal platform functionality is working correctly
  7. 7. Confirm the vulnerability is remediated

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

Fix this in Unified Secops Platform Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5719 — 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-5719 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