High severity · published Oct 11, 2018
CVE-2018-1745
IBM Security Key Lifecycle Manager 2.7 and 3.0 could allow an unauthenticated user to restart the SKLM server due to missing authentication
7.5
CVSS
3.9%
EPSS
No
On KEV
Description
IBM Security Key Lifecycle Manager 2.7 and 3.0 could allow an unauthenticated user to restart the SKLM server due to missing authentication. IBM X-Force ID: 148424.
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
None
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)3.9% · higher than 90% 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.7.0 through 2.7.0.3; 3.0 through 3.0.0.1 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2018-1745
CVE.org
https://www.cve.org/CVERecord?id=CVE-2018-1745
Third Party Advisory
http://www.securityfocus.com/bid/105554
VDB Entry
https://exchange.xforce.ibmcloud.com/vulnerabilities/148424
Patch
https://www.ibm.com/support/docview.wss?uid=ibm10733355
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-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
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