dbcve.org
Unified Secops PlatformApplication · Logsign

CVE-2024-5717

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-24165.

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 by injecting malicious commands through unsanitized user input that is passed to a system call. Although authentication is required to exploit the flaw, the authentication mechanism can be bypassed, and the injected commands execute with root privileges.

MitigationImplement strict input validation and sanitization on all user-supplied parameters before using them in system calls, and remediate the authentication bypass vulnerability. Until a patch is available, restrict network access to the Logsign API to trusted sources only.

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. Verify Logsign Unified SecOps Platform is installed
    Identify whether the Logsign Unified SecOps Platform software is present on the system. Common methods include checking installed packages, scanning for the application directory, or querying the system inventory.
    Affected if Logsign Unified SecOps Platform is found on the system
  2. Check the installed product version
    Retrieve the installed version of Logsign Unified SecOps Platform. Compare the version number against the affected range: versions 6.4.6 through 6.4.7 (any version less than 6.4.8) are vulnerable.
    Affected if The installed version is 6.4.6, 6.4.7, or any version >= 6.4.6 but < 6.4.8
  3. Confirm HTTP API module is enabled
    Determine whether the HTTP API component of Logsign Unified SecOps Platform is enabled and accessible. This typically involves checking the service configuration, listening ports (such as port 443 or 8443), or API service status.
    Affected if The HTTP API is exposed and accepts connections
  4. Verify authentication mechanism status
    Assess whether the API authentication can be bypassed. The CVE indicates the authentication requirement can be circumvented, so test if unauthenticated requests to API endpoints are accepted.
    Affected if Unauthenticated access to the API is possible or authentication can be bypassed

The environment is affected if Logsign Unified SecOps Platform version 6.4.6 through 6.4.7 is installed with the HTTP API enabled and accessible, particularly if unauthenticated API access is possible.

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

Implement strict input validation and sanitization on all user-supplied parameters before using them in system calls, and remediate the authentication bypass vulnerability. Until a patch is available, restrict network access to the Logsign API to trusted sources only.

Recommended fix High confidence

6.4.8 or later

  1. Upgrade Logsign Unified SecOps Platform to version 6.4.8 or later to address the command injection vulnerability.
  2. Before upgrading, ensure you have a complete backup of the system and configuration.
  3. Review the upgrade documentation from Logsign support (support.logsign.net) for specific upgrade procedures.
  4. Test the upgrade in a non-production environment first if possible.
  5. After upgrading, verify the HTTP API functionality and confirm the vulnerability is remediated.
Caveat No specific breaking changes documented in the provided CVE description; standard upgrade precautions should be followed

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

Fix this in Unified Secops Platform Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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