IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 do not perform an authentication check for a critical resource or functionality allowing anonymous users access to protected areas.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Security_key_lifecycle_manager | Ibm | 2.5.0 (including) | 2.5.0 (including) |
| Security_key_lifecycle_manager | Ibm | 2.5.0.0 (including) | 2.5.0.0 (including) |
| Security_key_lifecycle_manager | Ibm | 2.5.0.1 (including) | 2.5.0.1 (including) |
| Security_key_lifecycle_manager | Ibm | 2.5.0.2 (including) | 2.5.0.2 (including) |
| Security_key_lifecycle_manager | Ibm | 2.5.0.3 (including) | 2.5.0.3 (including) |
| Security_key_lifecycle_manager | Ibm | 2.5.0.4 (including) | 2.5.0.4 (including) |
| Security_key_lifecycle_manager | Ibm | 2.5.0.5 (including) | 2.5.0.5 (including) |
| Security_key_lifecycle_manager | Ibm | 2.5.0.6 (including) | 2.5.0.6 (including) |
| Security_key_lifecycle_manager | Ibm | 2.5.0.7 (including) | 2.5.0.7 (including) |
| Security_key_lifecycle_manager | Ibm | 2.6.0 (including) | 2.6.0 (including) |
| Security_key_lifecycle_manager | Ibm | 2.6.0.1 (including) | 2.6.0.1 (including) |
| Security_key_lifecycle_manager | Ibm | 2.6.0.2 (including) | 2.6.0.2 (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: