First published: Wed Feb 01 2017(Updated: )
IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 can be deployed with active debugging code that can disclose sensitive information.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Security Guardium Key Lifecycle Manager | =2.5.0 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.0 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.1 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.2 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.3 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.4 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.5 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.6 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.7 | |
IBM Security Guardium Key Lifecycle Manager | =2.6.0 | |
IBM Security Guardium Key Lifecycle Manager | =2.6.0.1 | |
IBM Security Guardium Key Lifecycle Manager | =2.6.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-6117 is considered a medium severity vulnerability due to its potential to disclose sensitive information.
To fix CVE-2016-6117, disable the active debugging code in IBM Tivoli Key Lifecycle Manager.
CVE-2016-6117 affects IBM Tivoli Key Lifecycle Manager versions 2.5.0 to 2.6.0.2.
CVE-2016-6117 can disclose sensitive operational details and internal configurations.
Yes, IBM has released updates to address CVE-2016-6117, which should be applied to affected versions.