Security Bulletin: COGNOS DIRECT INTEGRATION ACCESS REMAINS OPEN AFTER CLOSING MAXIMO SESSION (CVE-2014-6102)

Summary

IBM Maximo Asset Management could allow a user to access Cognos BI even after the Maximo session is closed.

Vulnerability Details

CVE-ID: CVE-2014-6102

DESCRIPTION:

IBM Maximo Asset Management could allow a local user to bypass security on another user’s Maximo session due to it improperly logging out the previous user.

CVSS Base Score: 2.1

CVSS Temporal Score: See <https://exchange.xforce.ibmcloud.com/vulnerabilities/96141&gt; for the current score

CVSS Environmental Score*: Undefined

CVSS Vector: (AV:L/AC:L/Au:N/C:N/I:P/A:N)

Affected Products and Versions

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

Remediation/Fixes

_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:

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.

Workarounds and Mitigations

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.