Security Bulletin: IBM Security Key Lifecycle Manager is vulnerable to Incorrect Permission Assignment for Critical Resource (CVE-2018-1750)

Summary

IBM Security Key Lifecycle Manager specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. In case of Windows operating system, all user accounts with access to the system will have read access to all the application backups created in the SKLM_DATA folder.

Vulnerability Details

CVEID: CVE-2018-1750 DESCRIPTION: IBM Tivoli Key Lifecycle Manager specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
CVSS Base Score: 4.2
CVSS Temporal Score: See <https://exchange.xforce.ibmcloud.com/vulnerabilities/148511&gt; for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N)

Affected Products and Versions

IBM Security Key Lifecycle Manager: v3.0- 3.0.0.1

IBM Security Key Lifecycle Manager: v2.7- 2.7.0.4

IBM Security Key Lifecycle Manager: v2.6- 2.6.0.5

Remediation/Fixes

Product

| VRMF | Remediation/First Fix
—|—|—
IBM Security Key Lifecycle Manager | 3.0- 3.0.0.1 | 3.0.0-ISS-SKLM-FP0002

On LNUX servers, there is a sklmPermission.sh sklmPermissions.sh script provided from 3.0.0-ISS-SKLM-FP0002 onwards.

1. Execute the sklmPermission.sh script
2. Reboot system.
3. After every reboot for multi-master configuration, user needs to set following parameters:
   sysctl -w kernel.msgmni=16384
   sysctl -w kernel.sem=“250 32000 100 1024”

Workarounds and Mitigations

For Windows server, as a workaround, windows users can change or remove the read access to all users except Administrator.