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

> Authenticated attackers can read or write server files via crafted requests, potentially leading to code execution through .xview files.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 29 May 2024
- **Updated:** 27 Sep 2024

## What is CVE-2024-36427?

CVE-2024-36427 is a high-severity path traversal vulnerability in n/a, published on 29 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The file-serving function in TARGIT Decision Suite before 24.06.19002 (TARGIT Decision Suite 2024 – June) allows authenticated attackers to read or write to server files via a crafted file request. This can allow code execution via a .xview file.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2024-36427 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36427 is a high-severity path traversal vulnerability in n/a, published on 29 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36427 exists.

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

## Sources

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

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