CVE Vulnerabilities

CVE-2015-5017

Improper Access Control

Published: Jan 03, 2016 | Modified: Jan 06, 2016
CVSS 3.x
5.4
MEDIUM
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
CVSS 2.x
5.5 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:N
RedHat/V2
RedHat/V3
Ubuntu

IBM Maximo Asset Management 7.1 through 7.1.1.13, 7.5.0 before 7.5.0.8 IFIX005, and 7.6.0 before 7.6.0.2 IFIX002; Maximo Asset Management 7.5.0 before 7.5.0.8 IFIX005, 7.5.1, and 7.6.0 before 7.6.0.2 IFIX002 for SmartCloud Control Desk; and Maximo Asset Management 7.1 through 7.1.1.13 and 7.2 for Tivoli IT Asset Management for IT and certain other products allow remote authenticated users to bypass intended access restrictions and establish a login session by entering an expired password.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Maximo_for_transportation Ibm 7.5 7.5
Maximo_for_utilities Ibm 7.5 7.5
Maximo_for_utilities Ibm 7.1 7.1
Maximo_for_nuclear_power Ibm 7.1 7.1
Tivoli_service_request_manager Ibm 7.1 7.1
Maximo_asset_management Ibm 7.5 7.5
Smartcloud_control_desk Ibm 7.5 7.5
Maximo_for_life_sciences Ibm 7.6 7.6
Smartcloud_control_desk Ibm 7.6 7.6
Change_and_configuration_management_database Ibm 7.1 7.1
Maximo_asset_management_essentials Ibm 7.5 7.5
Tivoli_asset_management_for_it Ibm 7.2 7.2
Maximo_asset_management Ibm 7.1 7.1
Maximo_for_oil_and_gas Ibm 7.1 7.1
Maximo_for_government Ibm 7.1 7.1
Change_and_configuration_management_database Ibm 7.2 7.2
Maximo_for_energy_optimization Ibm 7.1 7.1
Maximo_for_life_sciences Ibm 7.5 7.5
Tivoli_asset_management_for_it Ibm 7.1 7.1
Maximo_for_nuclear_power Ibm 7.5 7.5
Maximo_for_government Ibm 7.5 7.5
Maximo_asset_management Ibm 7.6 7.6
Maximo_for_life_sciences Ibm 7.1 7.1
Tivoli_service_request_manager Ibm 7.2 7.2
Maximo_for_oil_and_gas Ibm 7.5 7.5
Maximo_for_transportation Ibm 7.1 7.1
Maximo_asset_management_essentials Ibm 7.1 7.1

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References