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.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Cloud_orchestrator | Ibm | 2.4 (including) | 2.4 (including) |
| Cloud_orchestrator | Ibm | 2.4.0.1 (including) | 2.4.0.1 (including) |
| Cloud_orchestrator | Ibm | 2.4.0.2 (including) | 2.4.0.2 (including) |
| Cloud_orchestrator | Ibm | 2.4.0.3 (including) | 2.4.0.3 (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 | 2.3.0.1 (including) | 2.3.0.1 (including) |
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: