First published: Thu Feb 02 2017(Updated: )
IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. An attacker could exploit this vulnerability to obtain sensitive information using man in the middle techniques.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Security Key Lifecycle Manager | =2.5.0 | |
IBM Security Key Lifecycle Manager | =2.5.0.0 | |
IBM Security Key Lifecycle Manager | =2.5.0.1 | |
IBM Security Key Lifecycle Manager | =2.5.0.2 | |
IBM Security Key Lifecycle Manager | =2.5.0.3 | |
IBM Security Key Lifecycle Manager | =2.5.0.4 | |
IBM Security Key Lifecycle Manager | =2.5.0.5 | |
IBM Security Key Lifecycle Manager | =2.5.0.6 | |
IBM Security Key Lifecycle Manager | =2.5.0.7 | |
IBM Security Key Lifecycle Manager | =2.6.0 | |
IBM Security Key Lifecycle Manager | =2.6.0.1 | |
IBM Security 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-6116 has been rated as moderate severity due to the potential for sensitive information disclosure.
To fix CVE-2016-6116, ensure that HTTP Strict Transport Security is properly enabled in your IBM Tivoli Key Lifecycle Manager configuration.
CVE-2016-6116 affects IBM Tivoli Key Lifecycle Manager versions 2.5.0 through 2.6.0.2.
Yes, an attacker can exploit CVE-2016-6116 remotely through man-in-the-middle techniques.
Yes, CVE-2016-6116 poses a risk of sensitive data exposure if exploited.