First published: Thu Jan 04 2018(Updated: )
IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 133557.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Security Guardium Key Lifecycle Manager | =2.5.0 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.0 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.1 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.2 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.3 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.4 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.5 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.6 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.7 | |
IBM Security Guardium Key Lifecycle Manager | =2.5.0.8 | |
IBM Security Guardium Key Lifecycle Manager | =2.6.0 | |
IBM Security Guardium Key Lifecycle Manager | =2.6.0.1 | |
IBM Security Guardium Key Lifecycle Manager | =2.6.0.2 | |
IBM Security Guardium Key Lifecycle Manager | =2.6.0.3 | |
IBM Security Guardium Key Lifecycle Manager | =2.7.0 | |
IBM Security Guardium Key Lifecycle Manager | =2.7.0.1 | |
IBM Security Guardium Key Lifecycle Manager | =2.7.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-1664 has been categorized as a medium severity vulnerability due to its potential impact on the confidentiality of sensitive information.
To fix CVE-2017-1664, upgrade your IBM Tivoli Key Lifecycle Manager to the latest version that addresses the use of weak cryptographic algorithms.
CVE-2017-1664 affects IBM Tivoli Key Lifecycle Manager versions 2.5, 2.6, and 2.7.
CVE-2017-1664 could allow attackers to decrypt highly sensitive information due to the use of weaker than expected cryptographic algorithms.
Yes, IBM has released updates for affected versions that mitigate the vulnerabilities described in CVE-2017-1664.