First published: Tue Feb 07 2017(Updated: )
IBM Tivoli Key Lifecycle Manager 2.0.1, 2.5, and 2.6 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
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.0 | |
IBM Security Guardium Key Lifecycle Manager | =2.6.0.1 | |
IBM Security Guardium Key Lifecycle Manager | =2.6.0.2 | |
IBM Security Key Lifecycle Manager | =2.0.1 | |
IBM Security Key Lifecycle Manager | =2.0.1.1 | |
IBM Security Key Lifecycle Manager | =2.0.1.2 | |
IBM Security Key Lifecycle Manager | =2.0.1.3 | |
IBM Security Key Lifecycle Manager | =2.0.1.4 | |
IBM Security Key Lifecycle Manager | =2.0.1.5 | |
IBM Security Key Lifecycle Manager | =2.0.1.6 | |
IBM Security Key Lifecycle Manager | =2.0.1.7 | |
IBM Security Key Lifecycle Manager | =2.0.1.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-6096 is classified as a medium severity vulnerability due to its potential for credentials disclosure.
To fix CVE-2016-6096, it is recommended to upgrade IBM Tivoli Key Lifecycle Manager to a version that is not affected by this vulnerability.
CVE-2016-6096 affects IBM Tivoli Key Lifecycle Manager versions 2.0.1, 2.5, and 2.6.
CVE-2016-6096 is a cross-site scripting (XSS) vulnerability.
Yes, CVE-2016-6096 can potentially lead to credentials disclosure, which may facilitate unauthorized access to sensitive data.