Security Key Lifecycle Manager vulnerabilitiesRanked by how likely they are to be used.
Security Key Lifecycle Manager is made by IBM. We track 70 published vulnerabilities in it, across 68 versions. None of them is on the list of flaws known to be exploited today. If you run Security Key Lifecycle Manager, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Security Key Lifecycle Manager vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Security Key Lifecycle Manager's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Security Key Lifecycle Manager flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 3.9%CVE-2018-1745High
IBM Security Key Lifecycle Manager 2.7 and 3.0 could allow an unauthenticated user to restart the SKLM server due to missing authentication.
- 2.7%CVE-2017-1671High
IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 could allow a remote attacker to traverse directories on the system.
- 2.7%CVE-2016-6104High
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 attacker to execute arbitrary code on...
- 2.6%CVE-2018-1744Medium
IBM Security Key Lifecycle Manager 2.5, 2.6, 2.7, and 3.0 could allow a remote attacker to traverse directories on the system.
- 2.3%CVE-2020-4567Critical
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.
- 2.1%CVE-2016-6105High
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.
- 1.9%CVE-2020-4574High
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.
- 1.9%CVE-2017-1670Critical
IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 is vulnerable to SQL injection.
- 1.9%CVE-2018-1747High
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.
- 1.8%CVE-2016-6093Critical
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.
Running Security Key Lifecycle Manager? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Security Key Lifecycle Manager on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 70 published vulnerabilities listed under the name Security Key Lifecycle Manager, across 68 versions.
None of Security Key Lifecycle Manager's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Security Key Lifecycle Manager. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.