# CVE-2013-4172: Code injection in n/a

> Remote administrators can execute arbitrary Ruby code in Red Hat CloudForms Management Engine, posing a critical risk to cloud infrastructure integrity.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jhv9-pf4q-qvw6

## What is CVE-2013-4172?

CVE-2013-4172 is a high-severity code injection vulnerability in n/a, published on 23 Aug 2013. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Red Hat CloudForms Management Engine 5.1 allow remote administrators to execute arbitrary Ruby code via unspecified vectors.

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

## Which versions are affected by CVE-2013-4172?

It affects 1 product.


Products: Redhat Cloudforms Management Engine.

## How do I fix CVE-2013-4172?

Apply the vendor's patch.

## Is CVE-2013-4172 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2068](https://insights.sbomify.com/CVE-2013-2068/): Path traversal in n/a (critical 9.4)
- [CVE-2014-8164](https://insights.sbomify.com/CVE-2014-8164/): Security feature bypass in Red Hat CloudForms (critical 9.1)
- [CVE-2020-14324](https://insights.sbomify.com/CVE-2020-14324/): Command injection in CloudForms (critical 9.1)
- [CVE-2014-0087](https://insights.sbomify.com/CVE-2014-0087/): Missing authorization in n/a (high 8.8)
- [CVE-2016-7040](https://insights.sbomify.com/CVE-2016-7040/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4172 and fix it if it is affected.

What it is: CVE-2013-4172 is a high-severity code injection vulnerability in n/a, published on 23 Aug 2013. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4172 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-2013-4172/ (Markdown: https://insights.sbomify.com/CVE-2013-4172/index.md)
```

## Sources

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

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