IBM Maximo Asset Management is vulnerable to cross-site request forgery, caused by improper validation of user-supplied input. By persuading an authenticated user to visit a malicious Web site, a remote attacker could send a malformed HTTP request. An attacker could exploit this vulnerability to perform cross-site scripting attacks, Web cache poisoning, and other malicious activities.
DESCRIPTION:
Customers who have Maximo Asset Management, Maximo Asset Management Essentials, Maximo Industry Solutions (including Maximo for Government, Maximo for Nuclear Power, Maximo for Transportation, Maximo for Life Sciences, Maximo for Oil and Gas and Maximo for Utilities), Tivoli Asset Management for IT, Tivoli Service Request Manager, Change and Configuration Management Database, and SmartCloud Control Desk are potentially impacted by this vulnerability, which can cause issues related to integrity.
CVE-2014-3024
CVSS Base Score: 3.5
CVSS Temporal Score: See <https://exchange.xforce.ibmcloud.com/vulnerabilities/93063>
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:S/C:N/I:P/A:N)
APAR: IV56643
1. Maximo Asset Management 7.5, 7.1
2. Maximo Asset Management Essentials 7.5, 7.1
3. Maximo for Government 7.5, 7.1
4. Maximo for Nuclear Power 7.5, 7.1
5. Maximo for Transportation 7.5, 7.1
6. Maximo for Life Sciences 7.5, 7.1
7. Maximo for Oil and Gas 7.5, 7.1
8. Maximo for Utilities 7.5, 7.1
9. SmartCloud Control Desk 7.5
10. Tivoli Asset Management for IT 7.2, 7.1
11. Tivoli Service Request Manager 7.2, 7.1
12. Change and Configuration Management Database 7.2, 7.1
It is likely that earlier versions of affected products are also affected by these vulnerabilities. Remediation is not provided for product versions that are no longer supported. IBM recommends that customers upgrade to the latest supported version of products in order to obtain remediation for the vulnerabilities.
_VENDOR FIXES: _
The recommended solution is to download the appropriate Interim Fix or Fix Pack from Fix Central (What is Fix Central?) and apply for each affected product as soon as possible. Please see below for information on the fixes available for each product, version, and release. Follow the installation instructions in the βreadmeβ documentation provided with each fix pack or interim fix.
For Maximo Asset Management, Maximo Asset Management Essentials and Maximo Industry Solutions 7.5, 7.1:
VRMF | Fix Pack or Interim Fix | **Download ** |
---|---|---|
7.5.0.6 | Maximo 7.5.0.6 Interim Fix: | |
7.5.0.6-TIV-MAM-IFIX002 or latest Interim Fix available | FixCentral | |
7.1.1.12 | 7.1.1.12 Interim Fix: | |
MBS_71112_LAFIX.20140625-1402 or latest Interim Fix available | Contact IBM Support |
**For SmartCloud Control Desk 7.5:**VRMF | Fix Pack or Interim Fix | **Download ** |
---|---|---|
7.5.0.3 | Maximo 7.5.0.6 Interim Fix: | |
7.5.0.6-TIV-MAM-IFIX002 or latest Interim Fix available | FixCentral | |
7.5.1.2 | Maximo 7.5.0.6 Interim Fix: | |
7.5.0.6-TIV-MAM-IFIX002 or latest Interim Fix available | FixCentral |
For Tivoli IT Asset Management for IT, Tivoli Service Request Manager, and Change and Configuration Management Database 7.2, 7.1****VRMF | Fix Pack or Interim Fix | **Download ** |
---|---|---|
7.1.1.12 | 7.1.1.12 Interim Fix: | |
MBS_71112_LAFIX.20140625-1402 or latest Interim Fix available | Contact IBM Support |
If assistance is needed in determining the appropriate Fix Pack or Interim Fix level, contact IBM Technical Support. It is recommended that you always request the latest available Fix Pack or Interim Fix.
Due to the threat posed by a successful attack, IBM strongly recommends that customers apply fixes as soon as possible.
Until you apply the fixes, it may be possible to reduce the risk of successful attack by restricting network protocols required by an attack. For attacks that require certain privileges or access to certain packages, removing the privileges or the ability to access the packages from unprivileged users may help reduce the risk of successful attack. Both approaches may break application functionality, so IBM strongly recommends that customers test changes on non-production systems. Neither approach should be considered a long-term solution as neither corrects the underlying problem.