First published: Fri Jan 05 2018(Updated: )
IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 could allow a remote attacker to conduct phishing attacks, using an open redirect attack. By persuading a victim to visit a specially-crafted Web site, a remote attacker could exploit this vulnerability to spoof the URL displayed to redirect a user to a malicious Web site that would appear to be trusted. This could allow the attacker to obtain highly sensitive information or conduct further attacks against the victim. IBM X-Force ID: 133562.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Security Key Lifecycle Manager | =2.5.0 | |
IBM Security Key Lifecycle Manager | =2.5.0.1 | |
IBM Security Key Lifecycle Manager | =2.5.0.2 | |
IBM Security Key Lifecycle Manager | =2.5.0.3 | |
IBM Security Key Lifecycle Manager | =2.5.0.4 | |
IBM Security Key Lifecycle Manager | =2.5.0.5 | |
IBM Security Key Lifecycle Manager | =2.5.0.6 | |
IBM Security Key Lifecycle Manager | =2.5.0.7 | |
IBM Security Key Lifecycle Manager | =2.5.0.8 | |
IBM Security Key Lifecycle Manager | =2.6.0 | |
IBM Security Key Lifecycle Manager | =2.6.0.1 | |
IBM Security Key Lifecycle Manager | =2.6.0.2 | |
IBM Security Key Lifecycle Manager | =2.6.0.3 | |
IBM Security Key Lifecycle Manager | =2.7.0 | |
IBM Security Key Lifecycle Manager | =2.7.0.1 | |
IBM Security 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-1668 has a moderate severity rating, allowing potential phishing attacks through an open redirect.
To fix CVE-2017-1668, apply the latest patches or updates provided by IBM for affected versions of Tivoli Key Lifecycle Manager.
CVE-2017-1668 affects IBM Tivoli Key Lifecycle Manager versions 2.5, 2.6, and 2.7.
CVE-2017-1668 can be exploited via phishing attacks that use open redirect techniques.
Using IBM Tivoli Key Lifecycle Manager with CVE-2017-1668 may expose your users to phishing risks, so it is advisable to mitigate the vulnerability promptly.