# CVE-2024-36267: Path traversal in Redmine DMSF Plugin

> A logged-in user can read or delete arbitrary files on the server via path traversal in the Redmine DMSF Plugin.

- **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:** 30 May 2024
- **Updated:** 2 Aug 2024

## What is CVE-2024-36267?

CVE-2024-36267 is a high-severity path traversal vulnerability in Kontron Redmine DMSF Plugin, published on 30 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Path traversal vulnerability exists in Redmine DMSF Plugin versions prior to 3.1.4. If this vulnerability is exploited, a logged-in user may obtain or delete arbitrary files on the server (within the privilege of the Redmine process).

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2024-36267 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36267 is a high-severity path traversal vulnerability in Kontron Redmine DMSF Plugin, published on 30 May 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-36267 in the wild and no public exploit code.

Affected product: Kontron Redmine DMSF Plugin. 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-36267/ (Markdown: https://insights.sbomify.com/CVE-2024-36267/index.md)
```

## Sources

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

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