First published: Wed Jan 03 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: 133559.
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 | |
Debian Linux | =9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-1665 is considered to have a medium severity due to the potential for unauthorized decryption of sensitive information.
To fix CVE-2017-1665, upgrade IBM Tivoli Key Lifecycle Manager to a version that utilizes stronger cryptographic algorithms.
CVE-2017-1665 affects IBM Tivoli Key Lifecycle Manager versions 2.5, 2.6, and 2.7.
CVE-2017-1665 can allow attackers to decrypt sensitive information, potentially leading to data breaches.
As of now, there have been no public reports indicating active exploitation of CVE-2017-1665.