IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 discloses sensitive information in error messages that could aid an attacker in further attacks against the system. IBM X-Force ID: 134869.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Security_key_lifecycle_manager | Ibm | 2.6.0.2 | 2.6.0.2 |
Security_key_lifecycle_manager | Ibm | 2.6.0 | 2.6.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 |
Security_key_lifecycle_manager | Ibm | 2.5.0.7 | 2.5.0.7 |
Security_key_lifecycle_manager | Ibm | 2.5.0.3 | 2.5.0.3 |
Security_key_lifecycle_manager | Ibm | 2.6.0.1 | 2.6.0.1 |
Security_key_lifecycle_manager | Ibm | 2.5.0.8 | 2.5.0.8 |
Security_key_lifecycle_manager | Ibm | 2.6.0.3 | 2.6.0.3 |
Security_key_lifecycle_manager | Ibm | 2.7.0 | 2.7.0 |
Security_key_lifecycle_manager | Ibm | 2.7.0.1 | 2.7.0.1 |
Security_key_lifecycle_manager | Ibm | 2.7.0.2 | 2.7.0.2 |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: