CVE-2024-5722

Root code execution via hard-coded HTTP API key

Published Nov 22, 2024 · Updated Nov 26, 2024

Hard-coded cryptographic key use in Logsign Unified SecOps Platform 6.4.6 through 6.4.7 allows network-adjacent attackers to execute code. The HTTP API uses a cryptographic key embedded in the product instead of a deployment-specific secret, exposing the same trust material across installations. No authentication is required, but access must originate from an adjacent network; successful exploitation runs arbitrary code as root.

CVSS severity8.8
High
EPSS probability1.10%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Hard-coded cryptographic key use in Logsign Unified SecOps Platform 6.4.6 through 6.4.7 allows network-adjacent attackers to execute code. The HTTP API uses a cryptographic key embedded in the product instead of a deployment-specific secret, exposing the same trust material across installations. No authentication is required, but access must originate from an adjacent network; successful exploitation runs arbitrary code as root.

The record

CVE
CVE-2024-5722
Published
Nov 22, 2024
Updated
Nov 26, 2024
Vendor
Logsign
Product
Logsign Unified SecOps Platform
Classifications
CWE-321, CWE-798, T1190
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Nov 22, 2024CVE publishedPublication date reported by the CVE source.
  2. Nov 26, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.4.6
  2. Affected versionversion=6.4.6 <6.4.8

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Logsign · Logsign Unified SecOps Platformversion=6.4.6; version=6.4.6 <6.4.8

Published CVSS scores

8.8Zero Day InitiativeCVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-321Use of Hard-coded Cryptographic Key
CWE-798Use of Hard-coded Credentials
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo