# CVE-2024-5721: Logsign Unified SecOps Platform Missing Authentication Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code as root via the unauthenticated cluster HTTP API when enabled.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2024
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-6cfx-9cwr-vx7q

## What is CVE-2024-5721?

CVE-2024-5721 is a high-severity missing authorization vulnerability in Logsign Unified SecOps Platform, published on 22 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2024-5721?

It affects 1 product.


Products: Logsign Unified Secops Platform.

## How do I fix CVE-2024-5721?

No fix has been published for CVE-2024-5721 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-5721 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5721 exists.

Public exploit code:

- Logsign Remote Command Injection (metasploit)

## Other vulnerabilities in Logsign Unified SecOps Platform

- [CVE-2025-1044](https://insights.sbomify.com/CVE-2025-1044/): Logsign Unified SecOps Platform Authentication Bypass Vulnerability (critical 9.8)
- [CVE-2024-5717](https://insights.sbomify.com/CVE-2024-5717/): Logsign Unified SecOps Platform Command Injection Remote Code Execution Vulnerability (high 8.8)
- [CVE-2024-5719](https://insights.sbomify.com/CVE-2024-5719/): Logsign Unified SecOps Platform Command Injection Remote Code Execution Vulnerability (high 8.8)
- [CVE-2024-5720](https://insights.sbomify.com/CVE-2024-5720/): Logsign Unified SecOps Platform Command Injection Remote Code Execution Vulnerability (high 8.8)
- [CVE-2024-5722](https://insights.sbomify.com/CVE-2024-5722/): Logsign Unified SecOps Platform HTTP API Hard-coded Cryptographic Key Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5721 and fix it if it is affected.

What it is: CVE-2024-5721 is a high-severity missing authorization vulnerability in Logsign Unified SecOps Platform, published on 22 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5721 exists.

Affected product: Logsign Unified SecOps Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-5721/ (Markdown: https://insights.sbomify.com/CVE-2024-5721/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-5721
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-5721
- OSV: https://osv.dev/vulnerability/CVE-2024-5721

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-5721/
Summaries are generated and may contain mistakes; the official description above is the record.