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

> Remote attackers can execute arbitrary code via variable injection in Caldera directory manager parameters.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8jf4-r324-j6m9

## What is CVE-2014-2936?

CVE-2014-2936 is a high-severity code injection vulnerability in n/a, published on 8 May 2014. It can be exploited over the network, with no action from the victim.

### Official description

The directory manager in Caldera 9.20 allows remote attackers to conduct variable-injection attacks in the global scope via (1) the maindir_hotfolder parameter to dirmng/index.php, or an unspecified parameter to (2) PPD/index.php, (3) dirmng/docmd.php, or (4) dirmng/param.php.

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

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

It affects 1 product.


Products: Caldera Caldera.

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

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

## Is CVE-2014-2936 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2935](https://insights.sbomify.com/CVE-2014-2935/): Command injection in n/a (critical 10.0)
- [CVE-2014-2934](https://insights.sbomify.com/CVE-2014-2934/): SQL injection in n/a (high 7.5)
- [CVE-2014-2933](https://insights.sbomify.com/CVE-2014-2933/): Directory traversal vulnerability in dirmng/index.php in Caldera 9.20 allows remote attackers to access arbitrary directories via a crafted pathname. (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2936 is a high-severity code injection vulnerability in n/a, published on 8 May 2014. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2936 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-2936/ (Markdown: https://insights.sbomify.com/CVE-2014-2936/index.md)
```

## Sources

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

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