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

> An attacker can delete arbitrary files via crafted SAML state parameters, causing authentication outages in Logpoint SIEM.

- **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:** 27 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2024-36383?

CVE-2024-36383 is a medium-severity path traversal vulnerability in n/a, published on 27 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 SAML Authentication before 6.0.3. An attacker can place a crafted filename in the state field of a SAML SSO-URL response, and the file corresponding to this filename will ultimately be deleted. This can lead to a SAML Authentication login outage.

Weakness: CWE-706 (Use of Incorrectly-Resolved Name or Reference)

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

It affects 1 product.


Products: Logpoint Saml Authentication.

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

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

## Is CVE-2024-36383 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36383 is a medium-severity path traversal vulnerability in n/a, published on 27 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-36383 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-36383/ (Markdown: https://insights.sbomify.com/CVE-2024-36383/index.md)
```

## Sources

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

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