# CVE-2016-7040: Command injection in n/a

> Authenticated users can execute arbitrary shell commands in Red Hat CloudForms via malicious regular expressions in the API or UI.

- **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:** 7 Oct 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7fr4-2q4f-xgw5, RHSA-2016:1996

## What is CVE-2016-7040?

CVE-2016-7040 is a high-severity command injection vulnerability in n/a, published on 7 Oct 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Red Hat CloudForms Management Engine 4.1 does not properly handle regular expressions passed to the expression engine via the JSON API and the web-based UI, which allows remote authenticated users to execute arbitrary shell commands by leveraging the ability to view and filter collections.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cfme` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:5.6.2.1-1.el7cf |
| `cfme-appliance` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:5.6.2.1-1.el7cf |
| `cfme-appliance-debuginfo` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:5.6.2.1-1.el7cf |
| `cfme-debuginfo` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:5.6.2.1-1.el7cf |
| `cfme-gemset` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:5.6.2.1-1.el7cf |
| `rh-ruby22-rubygem-nokogiri` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:1.6.8-1.el7cf |
| `rh-ruby22-rubygem-nokogiri-debuginfo` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:1.6.8-1.el7cf |
| `rh-ruby22-rubygem-pkg-config` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:1.1.7-1.el7cf |
| `rh-ruby22-rubygem-pkg-config-doc` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:1.1.7-1.el7cf |
| `rh-ruby22-rubygem-thin` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:1.7.0-1.el7cf |
| `rh-ruby22-rubygem-thin-debuginfo` | Red Hat:cloudforms_managementengine:5.6::el7 | All versions | 0:1.7.0-1.el7cf |

Products: Redhat Cloudforms Management Engine.

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

Apply the vendor's patch.

## Is CVE-2016-7040 being exploited?

There is no known exploitation of CVE-2016-7040 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-2013-4172](https://insights.sbomify.com/CVE-2013-4172/): Code injection in n/a (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-7040 is a high-severity command injection vulnerability in n/a, published on 7 Oct 2016. 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-7040 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-2016-7040/ (Markdown: https://insights.sbomify.com/CVE-2016-7040/index.md)
```

## Sources

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

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