# CVE-2024-9257: Logsign Unified SecOps Platform delete_gsuite_key_file Input Validation Arbitrary File Deletion Vulnerability

> Authenticated attackers can delete arbitrary files on Logsign Unified SecOps Platform due to improper input validation in the delete_gsuite_key_file endpoint.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2024
- **Updated:** 23 Nov 2024
- **Also known as:** GHSA-q5px-fpgh-4rxw

## What is CVE-2024-9257?

CVE-2024-9257 is a medium-severity path traversal vulnerability in Logsign Unified SecOps Platform, published on 22 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Logsign Unified SecOps Platform delete_gsuite_key_file Input Validation Arbitrary File Deletion Vulnerability. This vulnerability allows remote attackers to delete arbitrary files within sensitive directories on affected installations of Logsign Unified SecOps Platform. Authentication is required to exploit this vulnerability.

The specific flaw exists within the delete_gsuite_key_file endpoint. The issue results from the lack of proper validation of a user-supplied filename prior to using it in file operations. An attacker can leverage this vulnerability to delete critical files on the system. Was ZDI-CAN-25265.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Logsign Unified Secops Platform.

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

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

## Is CVE-2024-9257 being exploited?

There is no known exploitation of CVE-2024-9257 in the wild and no public exploit code.

## 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-9257 and fix it if it is affected.

What it is: CVE-2024-9257 is a medium-severity path traversal vulnerability in Logsign Unified SecOps Platform, published on 22 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-9257 in the wild and no public exploit code.

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-9257/ (Markdown: https://insights.sbomify.com/CVE-2024-9257/index.md)
```

## Sources

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

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