CVE Vulnerabilities

CVE-2017-2664

Improper Access Control

Published: Jul 26, 2018 | Modified: Nov 21, 2024
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
CVSS 2.x
4 MEDIUM
AV:N/AC:L/Au:S/C:N/I:P/A:N
RedHat/V2
RedHat/V3
6.5 IMPORTANT
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Ubuntu

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

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Cloudforms Redhat 4.2 (including) 4.2 (including)
Cloudforms Redhat 4.6 (including) 4.6 (including)
Cloudforms_management_engine Redhat * 5.7.3 (excluding)
Cloudforms_management_engine Redhat 5.8 (including) 5.8.1 (excluding)
CloudForms Management Engine 5.7 RedHat cfme-0:5.7.4.2-1.el7cf *
CloudForms Management Engine 5.7 RedHat cfme-appliance-0:5.7.4.2-1.el7cf *
CloudForms Management Engine 5.7 RedHat cfme-gemset-0:5.7.4.2-1.el7cf *
CloudForms Management Engine 5.7 RedHat rh-ruby23-rubygem-nokogiri-0:1.8.1-2.el7cf *
CloudForms Management Engine 5.8 RedHat ansible-0:2.3.0.0-1.el7 *
CloudForms Management Engine 5.8 RedHat ansible-tower-0:3.1.3-1.el7at *
CloudForms Management Engine 5.8 RedHat cfme-0:5.8.1.5-1.el7cf *
CloudForms Management Engine 5.8 RedHat cfme-appliance-0:5.8.1.5-1.el7cf *
CloudForms Management Engine 5.8 RedHat cfme-gemset-0:5.8.1.5-1.el7cf *
CloudForms Management Engine 5.8 RedHat rh-ruby23-rubygem-nokogiri-0:1.7.2-1.el7cf *

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References