SK
Product
Security Key Lifecycle Manager
70
CVEs
0
On KEV
9.8
Max CVSS
0
New 30D
Severity mix
Critical 6High 19Medium 41Low 4
Watch
Add Security Key Lifecycle Manager to your stack to get only the CVEs that touch what you run.
| CVE | CVSS | Published | Summary · affected versions |
|---|---|---|---|
| CVE-2023-25924 | 8.8 | Mar 22 | IBM Security Guardium Key Lifecycle Manager 3.0, 3.0.1, 4.0, 4.1, and 4.1.1 could allow an authenticated user to perform actions that they should not have access to due to… Affected: 3.0; 3.0.1; 4.0; 4.1; 4.1.1 |
| CVE-2017-1672 | 8.8 | Jan 4 | IBM Tivoli Key Lifecycle Manager 2.6 and 2.7 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted… Affected: 2.6.0; 2.6.0.1; 2.6.0.2; 2.6.0.3; 2.7.0; 2.7.0.1; +1 more |
| CVE-2016-6103 | 8.8 | Feb 2 | IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted… Affected: 2.5.0; 2.5.0.0; 2.5.0.1; 2.5.0.2; 2.5.0.3; 2.5.0.4; +6 more |
| CVE-2016-6105 | 8.2 | Feb 1 | IBM Tivoli Key Lifecycle Manager 2.5 and 2.6 do not perform an authentication check for a critical resource or functionality allowing anonymous users access to protected areas Affected: 2.5.0; 2.5.0.0; 2.5.0.1; 2.5.0.2; 2.5.0.3; 2.5.0.4; +6 more |
| CVE-2018-1750 | 8.1 | Oct 8 | IBM Security Key Lifecycle Manager 3.0 specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors Affected: 2.6.0 through 2.6.0.5; 2.7.0 through 2.7.0.4; 3.0; 3.0.0.1 |
| CVE-2017-1666 | 8.1 | Jan 9 | IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 is vulnerable to a XML External Entity Injection (XXE) attack when processing XML data Affected: 2.5.0; 2.5.0.1; 2.5.0.2; 2.5.0.3; 2.5.0.4; 2.5.0.5; +10 more |
| CVE-2016-6098 | 8.1 | Jun 8 | IBM Tivoli Key Lifecycle Manager 2.0.1, 2.5, and 2.6 specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended… Affected: 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 |
| CVE-2023-25923 | 7.5 | Mar 21 | IBM Security Guardium Key Lifecycle Manager 3.0, 3.0.1, 4.0, 4.1, and 4.1.1 could allow an attacker to upload files that could be used in a denial of service attack due to… Affected: 3.0; 3.0.1; 4.0; 4.1; 4.1.1 |
| CVE-2021-38984 | 7.5 | Nov 15 | IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information Affected: 3.0 through 3.0.0.4; 3.0.1 through 3.0.1.5; 4.0 through 4.0.0.3 |
| CVE-2021-38983 | 7.5 | Nov 15 | IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information Affected: 3.0 through 3.0.0.4; 3.0.1 through 3.0.1.5; 4.0 through 4.0.0.3; 4.1.0; 4.1.0.1; 4.1.1 |
| CVE-2021-38979 | 7.5 | Nov 15 | IBM Tivoli Key Lifecycle Manager 3.0, 3.0.1, 4.0, and 4.1 uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the software… Affected: 3.0 through 3.0.0.4; 3.0.1 through 3.0.1.5; 4.0 through 4.0.0.3; 4.1.0; 4.1.0.1; 4.1.1 |
| CVE-2020-4574 | 7.5 | Jul 29 | 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 Affected: 3.0.1; 4.0 |
| CVE-2019-4565 | 7.5 | Sep 20 | IBM Security Key Lifecycle Manager 3.0 and 3.0.1 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user… Affected: 3.0 through 3.0.0.2; 3.0.1 through 3.0.1.1 |
| CVE-2018-1751 | 7.5 | Jan 23 | IBM Security Key Lifecycle Manager 3.0 through 3.0.0.2 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information Affected: 3.0; 3.0.0.2 |
| CVE-2018-1745 | 7.5 | Oct 11 | IBM Security Key Lifecycle Manager 2.7 and 3.0 could allow an unauthenticated user to restart the SKLM server due to missing authentication Affected: 2.7.0 through 2.7.0.3; 3.0 through 3.0.0.1 |
| CVE-2017-1671 | 7.5 | Jan 9 | IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 could allow a remote attacker to traverse directories on the system Affected: 2.5.0; 2.5.0.1; 2.5.0.2; 2.5.0.3; 2.5.0.4; 2.5.0.5; +10 more |
| CVE-2016-6104 | 7.2 | Feb 7 | IBM Tivoli Key Lifecycle Manager 2.5, and 2.6 could allow a remote attacker to upload arbitrary files, caused by the improper validation of file extensions, which could allow the… Affected: 2.5.0; 2.5.0.0; 2.5.0.1; 2.5.0.2; 2.5.0.3; 2.5.0.4; +6 more |
| CVE-2018-1747 | 7.1 | Oct 15 | IBM Security Key Lifecycle Manager 2.5, 2.6, 2.7, and 3.0 is vulnerable to a XML External Entity Injection (XXE) attack when processing XML data Affected: 2.5.0 through 2.5.0.9; 2.6.0 through 2.6.0.4; 2.7.0 through 2.7.0.3; 3.0.0 through 3.0.0.1 |
| CVE-2018-1738 | 7.1 | Oct 11 | IBM Security Key Lifecycle Manager 2.6, 2.7, 3.0 could allow an authenticated user to obtain highly sensitive information or jeopardize system integrity due to improper… Affected: 2.6.0 through 2.6.0.4; 2.7.0 through 2.7.0.3; 3.0.0 through 3.0.0.1 |
Showing 19