dbcve.org
Unified Secops PlatformApplication · Logsign

CVE-2024-5722

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 →
93/100
Remediation priority · Urgent
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 HTTP API Hard-coded Cryptographic Key Remote Code Execution Vulnerability. This vulnerability allows network-adjacent 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 HTTP API. The issue results from using a hard-coded cryptographic key. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-24170.

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

Logsign Unified SecOps Platform contains a hard-coded cryptographic key in its HTTP API component. Attackers can exploit this key to bypass authentication and achieve remote code execution as the root user without any credentials. The vulnerability is remotely exploitable by network-adjacent attackers.

MitigationReplace the hard-coded cryptographic key with a properly generated, unique key; apply any available vendor patches; restrict network access to the HTTP API interface.

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

CVSS:3.0/AV:A/AC:L/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. Confirm Logsign Unified SecOps Platform is installed
    Look for Logsign processes running on the system (e.g., check running processes for 'logsign' or related service names), or check common installation directories for Logsign software.
    Affected if Logsign Unified SecOps Platform is not installed on the system.
  2. Check the installed version number
    Locate the version file or use the command-line tool to query the installed version (e.g., logsign --version or check /opt/logsign/version), then compare it against the affected range: >= 6.4.6 and < 6.4.8.
    Affected if The installed version falls within 6.4.6 to 6.4.7 inclusive.
  3. Determine if HTTP API component is enabled
    Inspect the Logsign configuration files or service settings to verify whether the HTTP API interface is enabled and accessible. This may involve checking configuration files in the installation directory or reviewing service startup parameters.
    Affected if The HTTP API component is enabled and network-accessible.
  4. Inspect for hardcoded cryptographic key in configuration
    Review HTTP API configuration files within the Logsign installation directory for the presence of a hardcoded cryptographic key. Look for static key values in configuration files related to API authentication.
    Affected if A hardcoded cryptographic key is found in the HTTP API configuration files.

You are affected if Logsign Unified SecOps Platform version 6.4.6 or 6.4.7 is running with the HTTP API component enabled and a hardcoded cryptographic key is present in the configuration.

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

Replace the hard-coded cryptographic key with a properly generated, unique key; apply any available vendor patches; restrict network access to the HTTP API interface.

Recommended fix High confidence

6.4.8 or later

  1. 1. Schedule a maintenance window for the upgrade
  2. 2. Back up the Logsign Unified SecOps Platform configuration and data according to vendor documentation
  3. 3. Download Logsign Unified SecOps Platform version 6.4.8 or later from the official support portal at support.logsign.net
  4. 4. Follow the vendor's documented upgrade procedure for applying the new version
  5. 5. After upgrade, verify the application is running correctly and all services are operational
  6. 6. Confirm the HTTP API is functioning properly and the hard-coded key has been removed or changed
Caveat Review release notes for any changes in functionality or configuration requirements between your current version and 6.4.8

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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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