CVE Vulnerabilities


Improper Access Control

Published: Feb 08, 2017 | Modified: Feb 14, 2017
CVSS 3.x
CVSS 2.x
1.7 LOW

A vulnerability has been identified in IBM Cloud Orchestrator services/[action]/launch API. An authenticated domain admin user might modify cross domain resources via a /services/[action]/launch API call, provided it would have been possible for the domain admin user to gain access to a resource identifier of the other domain.


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

Affected Software

Name Vendor Start Version End Version
Cloud_orchestrator Ibm 2.4 (including) 2.4 (including)
Cloud_orchestrator Ibm (including) (including)
Cloud_orchestrator Ibm (including) (including)
Cloud_orchestrator Ibm (including) (including)
Cloud_orchestrator Ibm 2.5 (including) 2.5 (including)
Cloud_orchestrator Ibm 2.5.01 (including) 2.5.01 (including)
Smartcloud_orchestrator Ibm 2.3 (including) 2.3 (including)
Smartcloud_orchestrator Ibm (including) (including)

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.