First published: Thu Feb 02 2017(Updated: )
IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials.
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-6095 is considered a medium severity vulnerability due to inadequate account lockout settings.
To fix CVE-2016-6095, configure stronger account lockout policies and ensure that failed login attempts are limited.
CVE-2016-6095 affects IBM Tivoli Key Lifecycle Manager versions 2.5.0 to 2.6.0.2.
Yes, CVE-2016-6095 can be exploited remotely by attackers attempting to brute force account credentials.
While there is no specific workaround for CVE-2016-6095, implementing strict account management practices can help mitigate risks.