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

> Remote attackers can execute arbitrary methods in Red Hat CloudForms via the ServiceController, leading to potential system compromise.

- **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:** Yes
- **Published:** 18 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6m4c-55qp-f477

## What is CVE-2014-0057?

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

### Official description

The x_button method in the ServiceController (vmdb/app/controllers/service_controller.rb) in Red Hat CloudForms 3.0 Management Engine 5.2 allows remote attackers to execute arbitrary methods via unspecified vectors.

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

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

It affects 2 products.


Products: Redhat Cloudforms, Redhat Cloudforms 3.0 Management Engine.

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

Apply the vendor's patch.

## Is CVE-2014-0057 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-14325](https://insights.sbomify.com/CVE-2020-14325/): Auth bypass in CloudForms (critical 9.1)
- [CVE-2014-0197](https://insights.sbomify.com/CVE-2014-0197/): Cross-site request forgery in CFME (high 8.8)
- [CVE-2016-5402](https://insights.sbomify.com/CVE-2016-5402/): Code injection in cfme (high 8.8)
- [CVE-2016-7071](https://insights.sbomify.com/CVE-2016-7071/): Missing authorization in CFME (high 8.8)
- [CVE-2017-7530](https://insights.sbomify.com/CVE-2017-7530/): Missing authorization in cfme (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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