IBM Security Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2.0, and 4.2.1 stores potentially sensitive information in log files that could be read by a local privileged user.
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_guardium_key_lifecycle_manager | Ibm | 4.1.0 (including) | 4.1.0 (including) |
| Security_guardium_key_lifecycle_manager | Ibm | 4.1.1 (including) | 4.1.1 (including) |
| Security_guardium_key_lifecycle_manager | Ibm | 4.2.0 (including) | 4.2.0 (including) |
| Security_guardium_key_lifecycle_manager | Ibm | 4.2.1 (including) | 4.2.1 (including) |
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: