# CVE-2016-5402: Code injection in cfme

> An authenticated attacker can execute arbitrary code by exploiting a code injection flaw in the capacity and utilization feature of Red Hat CloudForms.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 31 Oct 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6p9p-cwcr-3xj6, RHSA-2016:2839

## What is CVE-2016-5402?

CVE-2016-5402 is a high-severity code injection vulnerability in [UNKNOWN] cfme, published on 31 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A code injection flaw was found in the way capacity and utilization imported control files are processed. A remote, authenticated attacker with access to the capacity and utilization feature could use this flaw to execute arbitrary code as the user CFME runs as.

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

## Which versions are affected by CVE-2016-5402?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cfme` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:5.6.3.3-1.el7cf |
| `cfme-appliance` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:5.6.3.3-1.el7cf |
| `cfme-appliance-debuginfo` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:5.6.3.3-1.el7cf |
| `cfme-debuginfo` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:5.6.3.3-1.el7cf |
| `cfme-gemset` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:5.6.3.3-1.el7cf |
| `freeipmi` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:1.5.1-2.el7cf |
| `freeipmi-bmc-watchdog` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:1.5.1-2.el7cf |
| `freeipmi-debuginfo` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:1.5.1-2.el7cf |
| `freeipmi-devel` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:1.5.1-2.el7cf |
| `freeipmi-ipmidetectd` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:1.5.1-2.el7cf |
| `freeipmi-ipmiseld` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:1.5.1-2.el7cf |

Products: Redhat Cloudforms, Redhat Cloudforms Management Engine.

## How do I fix CVE-2016-5402?

Apply the vendor's patch.

## Is CVE-2016-5402 being exploited?

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

## Other vulnerabilities in [UNKNOWN] cfme

- [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-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)
- [CVE-2016-4471](https://insights.sbomify.com/CVE-2016-4471/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5402 and fix it if it is affected.

What it is: CVE-2016-5402 is a high-severity code injection vulnerability in [UNKNOWN] cfme, published on 31 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-5402 in the wild and no public exploit code.

Affected product: [UNKNOWN] cfme. 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-2016-5402/ (Markdown: https://insights.sbomify.com/CVE-2016-5402/index.md)
```

## Sources

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

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