Security Bulletin: Multiple Security Vulnerabilities affect IBM Cloud Private (CVE-2018-1060, CVE-2018-1061)

Summary

IBM Cloud Private and IBM Cloud Automation Manager component are vulnerable to multiple security vulnerabilities

Vulnerability Details

CVEID: CVE-2018-1060 DESCRIPTION: Python is vulnerable to a denial of service, caused by catastrophic backtracking in the pop3lib’s apop() method. A remote attacker could exploit this vulnerability to cause the application to crash.
CVSS Base Score: 6.5
CVSS Temporal Score: See <https://exchange.xforce.ibmcloud.com/vulnerabilities/145116&gt; for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H)

CVEID: CVE-2018-1061 DESCRIPTION: Python is vulnerable to a denial of service, caused by catastrophic backtracking in the difflib.IS_LINE_JUNK method. A remote attacker could exploit this vulnerability to cause the application to crash.
CVSS Base Score: 6.5
CVSS Temporal Score: See <https://exchange.xforce.ibmcloud.com/vulnerabilities/145115&gt; for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H)

Affected Products and Versions

IBM Cloud Private 2.1.0 – 3.1.0

Remediation/Fixes

For IBM Cloud Private 2.1.0.x - 3.1.0.x releases, upgrade to version 3.1.1

• You can obtain IBM Cloud Private 3.1.1 from IBM Passport Advantage

Upgrade instructions for IBM Cloud Automation Manager component are below:

You can upgrade the Pattern Manager and Software Repository docker containers that are created using Content Runtime template 2.1, 2.2 and 2.3. Before upgrading your Pattern Manager and Software Repository docker containers, make sure you have no middleware content template deployments, destructions or deletes in “Progress” state. If there are, then wait for them to complete before starting your upgrade.

Follow the steps below to upgrade your containers.

1. Log into Content Runtime System.

2. Find the image version using docker ps. If the image name is appended with 1.0-current, then you are using 1.0-current image. If the image name is appended with 2.0-current, then you are using 2.0-current image. (Example: If the image name is camc-pattern-manager:1.0-current then you are using 1.0-current and if the image name is camc-pattern-manager:2.0-current then you are using 2.0-current)

3. Execute the following command to update your container to the latest version of Pattern Manager and Software Repository docker containers. Execution of this command will upgrade both Pattern Manager and Software Repository docker container.

~/advanced-content-runtime/image-upgrade.sh camc-sw-repo <image-version>

Example:

If your current image version is 1.0-current then execute

~/advanced-content-runtime/image-upgrade.sh camc-sw-repo 1.0-current

If your current image version is 2.0-current then execute

~/advanced-content-runtime/image-upgrade.sh camc-sw-repo 2.0-current

4. To verify the upgrade, after successful execution of the above command, execute the following steps
a. Get the container ID of the containers using docker ps
b. Execute the following docker exec command to work on Pattern Manager container

docker exec -it <camc-pattern-manager-container-id> /bin/bash

c. In the Pattern Manager container execute python and you should see the following as python version

Python 2.7.15rc1

Execute cat /etc/os-release and you should see 18.04.1 LTS (Bionic Beaver) as Ubuntu version

d. Execute the following docker exec command to work on Software Repository container

docker exec -it <camc-software-repo-container-id> /bin/bash

e. In the Software Repository container execute python and you should see

bash: python: command not found

Execute cat /etc/os-release and you should see 18.04.1 LTS (Bionic Beaver) as Ubuntu version

Workarounds and Mitigations

None