InstallShield generates installation executables which are vulnerable to a DLL-planting that affects the IBM Tivoli Storage Manager (IBM Spectrum Protect) Server on Windows platforms.
CVEID: CVE-2016-2542**
DESCRIPTION:** Flexera InstallShield could allow a local attacker to gain elevated privileges on the system, caused by an untrusted search path. An attacker could exploit this vulnerability using a Trojan horse DLL in the current working directory of a setup-launcher executable file to gain elevated privileges on the system.
CVSS Base Score: 7.8
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/110914 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
The following levels of IBM Tivoli Storage Manager (IBM Spectrum Protect) Server are affected on the Windows platform:
This security exposure occurs only at installation time and does not affect already installed Tivoli Storage Manager servers.
If you are not installing a fixed level of the Tivoli Storage Manager Server (7.1.5 or 6.3.6), then the installation package is vulnerable to this security issue during installation and you must use the workaround provided below to prevent being exposed to the vulnerability.
Tivoli Storage Manager Server Release|First
Fixing
VRM Level|**_
Platform_|Link to Fix / Fix Availability Target**
—|—|—|—
7.1| 7.1.5| Windows | http://www.ibm.com/support/docview.wss?uid=swg24041864
6.3| 6.3.6| Windows| http://www.ibm.com/support/docview.wss?uid=swg24042544
6.2, 6.1, and 5.5|
| Windows| Upgrade to a fixed level (7.1.5 or 6.3.6) or use the workaround provided below.
This security exposure occurs only at installation time and does not affect already installed Tivoli Storage Manager servers.
To prevent exposure to this security vulnerability, download and run the installation package from a clean directory using the following steps:
If installation of a server package below the fixing level (7.1.5 or 6.3.6) or installation of a package for release 6.2 or below is required, then the above workaround should be used to avoid exposure to this vulnerability during the installation process. The workaround is not needed if the fixing level (7.1.5 or 6.3.6) or a higher level of the package is installed.