# CVE-2024-33858: Path traversal in n/a

> An attacker can write CSV files to arbitrary paths within the /tmp directory by manipulating the source_name parameter in Logpoint.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2024
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-frv5-mfr5-q7h5

## What is CVE-2024-33858?

CVE-2024-33858 is a medium-severity path traversal vulnerability in n/a, published on 7 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Logpoint before 7.4.0. A path injection vulnerability is seen while adding a CSV enrichment source. The source_name parameter could be changed to an absolute path; this will write the CSV file to that path inside the /tmp directory.

Weakness: CWE-91 (XML Injection)

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

It affects 1 product.


Products: Logpoint Siem.

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

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

## Is CVE-2024-33858 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-33857](https://insights.sbomify.com/CVE-2024-33857/): Server-side request forgery in n/a (critical 9.6)
- [CVE-2025-66359](https://insights.sbomify.com/CVE-2025-66359/): Cross-site scripting in SIEM (high 8.5)
- [CVE-2022-48684](https://insights.sbomify.com/CVE-2022-48684/): Code injection in n/a (high 8.4)
- [CVE-2022-48685](https://insights.sbomify.com/CVE-2022-48685/): Privilege escalation in n/a (high 7.7)
- [CVE-2024-48950](https://insights.sbomify.com/CVE-2024-48950/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-33858 is a medium-severity path traversal vulnerability in n/a, published on 7 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-33858 in the wild and no public exploit code.

Affected product: n/a. 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-33858/ (Markdown: https://insights.sbomify.com/CVE-2024-33858/index.md)
```

## Sources

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

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