IBM Security Key Lifecycle Manager 3.0 and 3.0.1 does not require that users should have…
Priority LOW 36CWE-521Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-521.
Summary
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 accounts. IBM X-Force ID: 166626.
Why it matters now
EPSS 0.01484 74th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2019-4565
- 2026-10-03 Alias added: GHSA-9hh3-q329-2qc2
References
More IBM Security Key Lifecycle Manager vulnerabilities
- TI-2020-03890 Missing brute-force protection in IBM Security Key Lifecycle Manager CVSS 3.1CRITICAL 9.8
- TI-2017-01308 SQL injection in IBM Security Key Lifecycle Manager CVSS 3.0CRITICAL 9.8
- TI-2016-05231 Credentials management flaw in IBM Security Key Lifecycle Manager CVSS 3.0CRITICAL 9.8
- TI-2016-05233 Improper access control in IBM Key Lifecycle Manager CVSS 3.0CRITICAL 9.8
- TI-2023-10962 IBM Security Key Lifecycle Manager SQL injection CVSS 3.1CRITICAL 9.8
- TI-2018-01538 Hard-coded credentials in IBM Security Key Lifecycle Manager CVSS 3.0CRITICAL 9.3
Sources
- CVE-2019-4565 · CVE Program
- CVE-2019-4565 · NVD
- FIRST EPSS
- GHSA-9hh3-q329-2qc2 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences