# CVE-2014-3642: Privilege escalation in n/a

> Remote authenticated users can gain privileges in Red Hat CloudForms via an insecure send method in the performance controller.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/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:** 6 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xjwp-9jvp-98jf

## What is CVE-2014-3642?

CVE-2014-3642 is a medium-severity vulnerability in n/a, published on 6 Oct 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

vmdb/app/controllers/application_controller/performance.rb in Red Hat CloudForms 3.1 Management Engine (CFME) before 5.3 allows remote authenticated users to gain privileges via unspecified vectors, related to an "insecure send method."

Weakness: CWE-264

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

It affects 6 products.


Products: Redhat Cloudforms 3.0.1 Management Engine, Redhat Cloudforms 3.0.2 Management Engine, Redhat Cloudforms 3.0.3 Management Engine, Redhat Cloudforms 3.0.4 Management Engine, Redhat Cloudforms 3.0.5 Management Engine, Redhat Cloudforms 3.0 Management Engine.

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

Upgrade to a fixed version.

## Is CVE-2014-3642 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-0140](https://insights.sbomify.com/CVE-2014-0140/): Missing authorization in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3642 is a medium-severity vulnerability in n/a, published on 6 Oct 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-3642 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-3642/ (Markdown: https://insights.sbomify.com/CVE-2014-3642/index.md)
```

## Sources

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

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