First published: Thu Jun 08 2017(Updated: )
IBM Tivoli Key Lifecycle Manager does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
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.0 | |
IBM Security Key Lifecycle Manager | =2.6.0.1 | |
IBM Security Key Lifecycle Manager | =2.6.0.2 | |
IBM Tivoli Key Lifecycle Manager | =2.0.1 | |
IBM Tivoli Key Lifecycle Manager | =2.0.1.1 | |
IBM Tivoli Key Lifecycle Manager | =2.0.1.2 | |
IBM Tivoli Key Lifecycle Manager | =2.0.1.3 | |
IBM Tivoli Key Lifecycle Manager | =2.0.1.4 | |
IBM Tivoli Key Lifecycle Manager | =2.0.1.5 | |
IBM Tivoli Key Lifecycle Manager | =2.0.1.6 | |
IBM Tivoli Key Lifecycle Manager | =2.0.1.7 | |
IBM Tivoli 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-6093 is considered to be of medium severity due to the risk of account compromise.
To fix CVE-2016-6093, configure IBM Tivoli Key Lifecycle Manager to enforce strong password policies.
CVE-2016-6093 affects multiple versions including 2.0.1.0 to 2.0.1.8 and 2.5.0.0 to 2.6.0.2.
CVE-2016-6093 is an authentication weakness due to insufficient password policy settings.
To mitigate the risks of CVE-2016-6093, regularly review and enforce strong password requirements in your organization.