Critical severity · published Jun 8, 2017
CVE-2016-6093
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
9.8
CVSS
1.8%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)1.8% · higher than 78% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
SK
Security Key Lifecycle Manager · Ibm
2.5.0.0; 2.5.0.1; 2.5.0.2; 2.5.0.3; 2.5.0.4; 2.5.0.5; +5 more · source: NVD
TK
Tivoli Key Lifecycle Manager · Ibm
2.0.1; 2.0.1.1; 2.0.1.2; 2.0.1.3; 2.0.1.4; 2.0.1.5; +3 more · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2016-6093
CVE.org
https://www.cve.org/CVERecord?id=CVE-2016-6093
Patch
http://www.ibm.com/support/docview.wss?uid=swg21997956
Third Party Advisory
http://www.securityfocus.com/bid/95985
VDB Entry
https://exchange.xforce.ibmcloud.com/vulnerabilities/118172
More from Security Key Lifecycle Manager
9.8
CVE-2023-25684
IBM Security Guardium Key Lifecycle Manager 3.0, 3.0.1, 4.0, 4.1, and 4.1.1 is vulnerable to SQL injection
9.8
CVE-2020-4567
IBM Tivoli Key Lifecycle Manager 3.0.1 and 4.0 uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials
9.8
CVE-2017-1670
IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 is vulnerable to SQL injection
9.8
CVE-2016-6095
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
9.3
CVE-2018-1742
IBM Tivoli Key Lifecycle Manager 2.6, 2.7, and 3.0 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication,…