Skip to content
Noroxi
CVE-2017-2632· NVD / CVE Program· CNA redhat

A logic error in valid_role() in CloudForms role validation before 5.7.1.3 could allow a tenant administrator to create groups with a higher

A logic error in valid_role() in CloudForms role validation before 5.7.1.3 could allow a tenant administrator to create groups with a higher privilege level than the tenant administrator should have. This would allow an attacker with tenant administration access to elevate privileges.

MediumCVSS 4.9 · v3.0—No exploit Fix available
Published
Jul 27, 2018
Updated
Jun 16, 2026
EPSS
1.5% · 73th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

19

Monitor

Low priority for now.

CVSS
19 / 40 · 4.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.5%

CNA vs NVD score

NVD
4.9
CNA · redhat
4.9
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
redhatcloudforms management engine
redhatcloudforms

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • redhat cloudforms4.2
  • redhat cloudforms management enginebefore 5.7.1.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • Red Hat cfme

    • 5.7.1.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Red Hat:cloudforms_managementengine:5.7::el7cfmebefore 0:5.7.1.3-1.el7cf0:5.7.1.3-1.el7cf
Red Hat:cloudforms_managementengine:5.7::el7cfme-appliancebefore 0:5.7.1.3-1.el7cf0:5.7.1.3-1.el7cf
Red Hat:cloudforms_managementengine:5.7::el7cfme-appliance-debuginfobefore 0:5.7.1.3-1.el7cf0:5.7.1.3-1.el7cf
Red Hat:cloudforms_managementengine:5.7::el7cfme-debuginfobefore 0:5.7.1.3-1.el7cf0:5.7.1.3-1.el7cf
Red Hat:cloudforms_managementengine:5.7::el7cfme-gemsetbefore 0:5.7.1.3-1.el7cf0:5.7.1.3-1.el7cf

Other highest-scoring records for the same primary product.

  • CVE-2013-2068Multiple directory traversal vulnerabilities in the AgentController in Red Hat CloudForms Management Engine 2.0 allow remote attackers to cr
    55Plan
  • CVE-2020-14324A high severity vulnerability was found in all active versions of Red Hat CloudForms before 5.11.7.0.
    37Monitor
  • CVE-2014-8164A insecure configuration for certificate verification (http.verify_mode = OpenSSL::SSL::VERIFY_NONE) may lead to verification bypass in Red
    36Monitor
  • CVE-2016-7071It was found that the CloudForms before 5.6.2.2, and 5.7.0.7 did not properly apply permissions controls to VM IDs passed by users.
    36Monitor
  • CVE-2014-0087The check_privileges method in vmdb/app/controllers/application_controller.rb in ManageIQ, as used in Red Hat CloudForms Management Engine (
    36Monitor
  • CVE-2016-7040Red Hat CloudForms Management Engine 4.1 does not properly handle regular expressions passed to the expression engine via the JSON API and t
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
red hat:cfme0:5.7.1.3-1.el7cf · Red Hat:cloudforms_managementengine:5.7::el7Package registry (OSV)
red hat:cfme-appliance0:5.7.1.3-1.el7cf · Red Hat:cloudforms_managementengine:5.7::el7Package registry (OSV)
red hat:cfme-appliance-debuginfo0:5.7.1.3-1.el7cf · Red Hat:cloudforms_managementengine:5.7::el7Package registry (OSV)
red hat:cfme-debuginfo0:5.7.1.3-1.el7cf · Red Hat:cloudforms_managementengine:5.7::el7Package registry (OSV)
red hat:cfme-gemset0:5.7.1.3-1.el7cf · Red Hat:cloudforms_managementengine:5.7::el7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records