CVE Vulnerabilities

CVE-2016-6098

Improper Access Control

Published: Jun 08, 2017 | Modified: Jun 13, 2017
CVSS 3.x
8.1
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CVSS 2.x
5.5 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:N
RedHat/V2
RedHat/V3
Ubuntu

IBM Tivoli Key Lifecycle Manager 2.0.1, 2.5, and 2.6 specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Tivoli_key_lifecycle_manager Ibm 2.0.1.6 2.0.1.6
Tivoli_key_lifecycle_manager Ibm 2.0.1.7 2.0.1.7
Tivoli_key_lifecycle_manager Ibm 2.0.1.4 2.0.1.4
Tivoli_key_lifecycle_manager Ibm 2.0.1.5 2.0.1.5
Security_key_lifecycle_manager Ibm 2.6.0.2 2.6.0.2
Security_key_lifecycle_manager Ibm 2.6.0.0 2.6.0.0
Security_key_lifecycle_manager Ibm 2.5.0.2 2.5.0.2
Security_key_lifecycle_manager Ibm 2.5.0.0 2.5.0.0
Security_key_lifecycle_manager Ibm 2.5.0.4 2.5.0.4
Security_key_lifecycle_manager Ibm 2.5.0.6 2.5.0.6
Security_key_lifecycle_manager Ibm 2.5.0.5 2.5.0.5
Security_key_lifecycle_manager Ibm 2.5.0.1 2.5.0.1
Tivoli_key_lifecycle_manager Ibm 2.0.1.1 2.0.1.1
Security_key_lifecycle_manager Ibm 2.5.0.7 2.5.0.7
Tivoli_key_lifecycle_manager Ibm 2.0.1 2.0.1
Tivoli_key_lifecycle_manager Ibm 2.0.1.8 2.0.1.8
Tivoli_key_lifecycle_manager Ibm 2.0.1.2 2.0.1.2
Security_key_lifecycle_manager Ibm 2.5.0.3 2.5.0.3
Tivoli_key_lifecycle_manager Ibm 2.0.1.3 2.0.1.3
Security_key_lifecycle_manager Ibm 2.6.0.1 2.6.0.1

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.

References