# CVE-2014-5339: Path traversal in n/a

> Authenticated attackers can write configuration files to arbitrary locations, potentially leading to code execution or system compromise.

- **Severity:** Medium 4.9 (`AV:N/AC:M/Au:S/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8mgc-hm3x-352v

## What is CVE-2014-5339?

CVE-2014-5339 is a medium-severity path traversal vulnerability in n/a, published on 2 Sep 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Check_MK before 1.2.4p4 and 1.2.5 before 1.2.5i4 allows remote authenticated users to write check_mk config files (.mk files) to arbitrary locations via vectors related to row selections.

## Which versions are affected by CVE-2014-5339?

It affects 1 product.


Products: Check Mk Project Check Mk.

## How do I fix CVE-2014-5339?

Upgrade to a fixed version.

## Is CVE-2014-5339 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5340](https://insights.sbomify.com/CVE-2014-5340/): Deserialization in n/a (critical 9.3)
- [CVE-2014-2331](https://insights.sbomify.com/CVE-2014-2331/): Code injection in n/a (high 8.5)
- [CVE-2014-2330](https://insights.sbomify.com/CVE-2014-2330/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2017-11507](https://insights.sbomify.com/CVE-2017-11507/): Cross-site scripting in Check MK (medium 6.1)
- [CVE-2017-9781](https://insights.sbomify.com/CVE-2017-9781/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-5339 and fix it if it is affected.

What it is: CVE-2014-5339 is a medium-severity path traversal vulnerability in n/a, published on 2 Sep 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-5339 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-2014-5339/ (Markdown: https://insights.sbomify.com/CVE-2014-5339/index.md)
```

## Sources

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

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