IBM Bluemix privileges management ⚔ [Disputed]

Summaryinfo

A vulnerability marked as critical has been reported in IBM Bluemix. This affects an unknown function. The manipulation leads to privileges management. The attack can be initiated remotely. Additionally, an exploit exists. There are still doubts about whether this vulnerability truly exists.

Detailsinfo

A vulnerability was found in IBM Bluemix (the affected version is unknown) and classified as critical. This issue affects an unknown code. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability.

The weakness was released 12/09/2016 by Oscar Martinez as Broken access control on bluemix containers as not defined mailinglist post (Full-Disclosure). It is possible to read the advisory at seclists.org. The public release was coordinated with IBM. The attack may be initiated remotely. A simple authentication is needed for exploitation. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK. The advisory points out:

It is assumed that a user with auditor role should not be able to create or delete containers.

A public exploit has been developed by Oscar Martinez and been published immediately after the advisory. The exploit is available at seclists.org. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 11 days. During that time the estimated underground price was around $5k-$25k. The real existence of this vulnerability is still doubted at the moment. The advisory illustrates:

1. Connect to bluemix using the cli CF with the user with "auditor" role. 1.1 cf login [-sso] 1.2 cf ic init 2. Show the images 2.1 cf ic images 3. Create the container 3.1 cf ic run --name broken_access_666 -p 8080 -m 512 registry.ng.bluemix.net/[your site]/[your image] example: cf ic run --name broken_access_666 -p 8080 -m 512 registry.ng.bluemix.net/mysite/tomcat 4. Delete your container cf ic stop [your container] cf ic rm [your container]

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• IBM

Name

• Bluemix

License

• commercial

Website

• Vendor: https://www.ibm.com/

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion