IBM Security Bulletin: IBM Maximo Asset Management could allow a remote attacker to hijack a user’s session, caused by the failure to invalidate an existing session identifier (CVE-2016-9977)

IBM Maximo Asset Management could allow a remote attacker to hijack a user’s session, caused by the failure to invalidate an existing session identifier. An attacker could exploit this vulnerability to gain access to another user’s session.

CVE(s): CVE-2016-9977

Affected product(s) and affected version(s):

This vulnerability affects the following versions of the IBM Maximo Asset Management core product, and all other IBM Maximo Industry Solution and IBM Control Desk products, regardless of their own version, if they are currently installed on top of an affected IBM Maximo Asset Management. *

Maximo Asset Management core product affected versions:
Maximo Asset Management 7.6, 7.5, 7.1
Maximo Asset Management Essentials 7.5, 7.1

Industry Solutions products affected if using an affected core version:
Maximo for Aviation
Maximo for Government
Maximo for Life Sciences
Maximo for Nuclear Power
Maximo for Oil and Gas
Maximo for Transportation
Maximo for Utilities

IBM Control Desk products affected if using an affected core version:
SmartCloud Control Desk
IBM Control Desk
Tivoli Asset Management for IT
Tivoli Integration Composer
Tivoli Service Request Manager
Tivoli Change and Configuration Management Database

* To determine the core product version, log in and view System Information. The core product version is the “Tivoli’s process automation engine” version. Please consult the Product Coexistence Matrix for a list of supported product combinations.

Refer to the following reference URLs for remediation and additional vulnerability details:
Source Bulletin: http://ift.tt/2roiNZa
X-Force Database: http://ift.tt/2qF1vKj

The post IBM Security Bulletin: IBM Maximo Asset Management could allow a remote attacker to hijack a user’s session, caused by the failure to invalidate an existing session identifier (CVE-2016-9977) appeared first on IBM PSIRT Blog.

from IBM Product Security Incident Response Team http://ift.tt/2rokIwG