# CVE-2014-2331: Code injection in n/a

> Authenticated attackers can execute arbitrary Python code via crafted snapshot files in Check_MK monitoring software.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **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:** 31 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w8wv-p5qh-jq8x

## What is CVE-2014-2331?

CVE-2014-2331 is a high-severity code injection vulnerability in n/a, published on 31 Aug 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Check_MK 1.2.2p2, 1.2.2p3, and 1.2.3i5 allows remote authenticated users to execute arbitrary Python code via a crafted rules.mk file in a snapshot.  NOTE: this can be exploited by remote attackers by leveraging CVE-2014-2330.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Check Mk Project Check Mk.

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

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

## Is CVE-2014-2331 being exploited?

There is no known exploitation of CVE-2014-2331 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-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)
- [CVE-2014-0243](https://insights.sbomify.com/CVE-2014-0243/): Path traversal in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2331 is a high-severity code injection vulnerability in n/a, published on 31 Aug 2015. 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-2331 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-2331/ (Markdown: https://insights.sbomify.com/CVE-2014-2331/index.md)
```

## Sources

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

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