IBM Maximo Asset Management installs with a default administrator account that a remote intruder could use to gain administrator access to the system. This vulnerability is due to an incomplete fix for CVE-2015-4966.
DESCRIPTION: IBM Maximo Asset Management installs with a default administrator account that a remote intruder could use to gain administrator access to the system. This vulnerability is due to an incomplete fix for CVE-2015-4966.
CVSS Base Score: 8.8
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/142116 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
Affected Products and Versions
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
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 Integration Composer
* 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.
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 7.6:
|VRM||Fix Pack, Feature Pack, or Interim Fix||Download|
|18.104.22.168||Maximo Asset Management 22.214.171.124 Fix Pack:
126.96.36.199-TIV-MAMKCNL-FP0001 or latest Interim Fix available
Workarounds and Mitigations
Additional Configuration for Existing Installations
Additional configuration is necessary for full protection on existing installations, even after application of Fix Pack or Interim Fix. Application of the Fix Pack or Interim Fix will allow simplified configuration of this security setting via a new property, mxe.int.allowdefaultlogin. On new installations, this property will already exist, and have the secure value of 0. However, administrators on existing installations must manually add the property and set the secure value after the application of the Fix Pack or Interim Fix. Manually adding the new property via these instructions without applying a Fix Pack or Interim Fix is also not sufficient for protection.
To manually add the mxe.int.allowdefaultlogin property to an existing installation after applying the appropriate Fix Pack or Interim Fix, please complete the following steps:
1. Log in as a user with access to the System Properties application.
2. From the System Properties application, click New Row to add a row to the Global Properties Table.
3. Use the following values to populate the new row. Leave other fields with their default values.
- Property Name: mxe.int.allowdefaultlogin
Description: Allow default login for MIF
Global Value: 0
Maximo Default: 0
4. Click Save. Then, check the checkbox for the row in the table containing the new property, and click Live Refresh. Click OK on the Live Refresh dialog.
Installation of the Fix Pack or Interim Fix above is the recommended remediation for this vulnerability for both new and existing installations. Application of the Fix Pack or Interim Fix will allow simplified configuration of this security setting via a new property, mxe.int.allowdefaultlogin.
However, new and existing installations with version levels earlier than the Fix Pack and Interim Fix levels specified above may manually apply an alternative fix. This alternative fix provides the same protection as application of the Fix Pack or Interim Fix, but will not allow simplified configuration of the security setting via the new property. If the fix in the Remediation/Fixes section has been applied and the mxe.int.allowdefaultlogin property is in use, the following manual configuration will have no effect.
To apply protection for this vulnerability without applying a Fix Pack or Interim Fix, please complete the following steps:
1. Navigate to the following file location: <maximo_root>\applications\maximo\mboejb\ejbmodule\META-INF
2. Open the ejb-jar.xml file.
3. Find all four instances of the following text. (You may Ctrl+F find "<env-entry-name>ALLOWDFLTLOGIN</env-entry-name>".)
4. In all four text blocks, change the <env-entry-value> from 1 to 0: <env-entry-value>0</env-entry-value>
5. Save the document. Delete the Maximo ear files, delete browser and app server caches, rebuild the maximo ear files, and redeploy.
Previous Bulletin Link CVE-2015-4966
Get Notified about Future Security Bulletins
30 July 2018: Original version published
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. In addition to other efforts to address potential vulnerabilities, IBM periodically updates the record of components contained in our product offerings. As part of that effort, if IBM identifies previously unidentified packages in a product/service inventory, we address relevant vulnerabilities regardless of CVE date. Inclusion of an older CVEID does not demonstrate that the referenced product has been used by IBM since that date, nor that IBM was aware of a vulnerability as of that date. We are making clients aware of relevant vulnerabilities as we become aware of them. "Affected Products and Versions" referenced in IBM Security Bulletins are intended to be only products and versions that are supported by IBM and have not passed their end-of-support or warranty date. Thus, failure to reference unsupported or extended-support products and versions in this Security Bulletin does not constitute a determination by IBM that they are unaffected by the vulnerability. Reference to one or more unsupported versions in this Security Bulletin shall not create an obligation for IBM to provide fixes for any unsupported or extended-support products or versions.
Was this topic helpful?
31 July 2018