CVE-2018-1745
First published: Thu Oct 11 2018(Updated: )
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.
Credit: psirt@us.ibm.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| IBM Security Key Lifecycle Manager | >=2.7.0<=2.7.0.3 | |
| IBM Security Key Lifecycle Manager | >=3.0<=3.0.0.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-1745?
CVE-2018-1745 has a medium severity level due to the potential for unauthorized server restarts.
How do I fix CVE-2018-1745?
To fix CVE-2018-1745, implement authentication controls for the SKLM server to prevent unauthorized access.
Who is affected by CVE-2018-1745?
CVE-2018-1745 affects IBM Security Key Lifecycle Manager versions 2.7 and 3.0.
What is the impact of CVE-2018-1745?
The impact of CVE-2018-1745 is that an unauthenticated user can restart the SKLM server, potentially disrupting services.
When was CVE-2018-1745 discovered?
CVE-2018-1745 was disclosed in 2018 as part of IBM's ongoing security assessments.
- agent/type
- agent/references
- agent/severity
- agent/remedy
- agent/weakness
- agent/author
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/softwarecombine
- vendor/ibm
- canonical/ibm security key lifecycle manager
- version/ibm security key lifecycle manager/2.7.0
- version/ibm security key lifecycle manager/2.7.0.3
- version/ibm security key lifecycle manager/3.0
- version/ibm security key lifecycle manager/3.0.0.1