# CVE-2017-2664: Missing authorization in CloudForms

> Attackers can escalate privileges by accessing unprotected methods in the CloudForms Rails application due to missing RBAC controls.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 26 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rc49-fxf8-jgg2, RHSA-2017:3484

## What is CVE-2017-2664?

CVE-2017-2664 is a medium-severity missing authorization vulnerability in Red Hat CloudForms, published on 26 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CloudForms Management Engine (cfme) before 5.7.3 and 5.8.x before 5.8.1 lacks RBAC controls on certain methods in the rails application portion of CloudForms. An attacker with access could use a variety of methods within the rails application portion of CloudForms to escalate privileges.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2017-2664?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cfme` | Red Hat:cloudforms_managementengine:5.7::el7 | All versions | 0:5.7.4.2-1.el7cf |
| `cfme-appliance` | Red Hat:cloudforms_managementengine:5.7::el7 | All versions | 0:5.7.4.2-1.el7cf |
| `cfme-appliance-debuginfo` | Red Hat:cloudforms_managementengine:5.7::el7 | All versions | 0:5.7.4.2-1.el7cf |
| `cfme-debuginfo` | Red Hat:cloudforms_managementengine:5.7::el7 | All versions | 0:5.7.4.2-1.el7cf |
| `cfme-gemset` | Red Hat:cloudforms_managementengine:5.7::el7 | All versions | 0:5.7.4.2-1.el7cf |
| `rh-ruby23-rubygem-nokogiri` | Red Hat:cloudforms_managementengine:5.7::el7 | All versions | 0:1.8.1-2.el7cf |
| `rh-ruby23-rubygem-nokogiri-debuginfo` | Red Hat:cloudforms_managementengine:5.7::el7 | All versions | 0:1.8.1-2.el7cf |
| `rh-ruby23-rubygem-nokogiri-doc` | Red Hat:cloudforms_managementengine:5.7::el7 | All versions | 0:1.8.1-2.el7cf |

Products: Redhat Cloudforms, Redhat Cloudforms Management Engine.

## How do I fix CVE-2017-2664?

Upgrade to a fixed version.

## Is CVE-2017-2664 being exploited?

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

## Other vulnerabilities in Red Hat CloudForms

- [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-2017-2664 and fix it if it is affected.

What it is: CVE-2017-2664 is a medium-severity missing authorization vulnerability in Red Hat CloudForms, published on 26 Jul 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-2017-2664 in the wild and no public exploit code.

Affected product: Red Hat CloudForms. 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-2017-2664/ (Markdown: https://insights.sbomify.com/CVE-2017-2664/index.md)
```

## Sources

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

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