First published: Tue Feb 07 2017(Updated: )
IBM Tivoli Key Lifecycle Manager 2.5, and 2.6 could allow a remote attacker to upload arbitrary files, caused by the improper validation of file extensions, which could allow the attacker to execute arbitrary code on the vulnerable system.
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.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.6.0 | |
IBM Security Key Lifecycle Manager | =2.6.0.1 | |
IBM Security Key Lifecycle Manager | =2.6.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2016-6104 is considered critical, as it allows remote attackers to execute arbitrary code on the vulnerable system.
To fix CVE-2016-6104, upgrade IBM Tivoli Key Lifecycle Manager to a patched version as recommended by the vendor.
CVE-2016-6104 affects versions 2.5 and 2.6 of IBM Tivoli Key Lifecycle Manager.
Yes, CVE-2016-6104 can be exploited remotely due to improper validation of file extensions.
CVE-2016-6104 allows a remote attacker to upload arbitrary files, potentially leading to arbitrary code execution.