dbcve.org
Change And Configuration Management DatabaseDatabase / datastore · Ibm

CVE-2015-4966

MEDIUM · 6.5 CVSS v2.0 Published 2015-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM Maximo Asset Management 7.1 through 7.1.1.13, 7.5.0 before 7.5.0.9 FP009, and 7.6.0 before 7.6.0.2 IFIX001; Maximo Asset Management 7.5.0 before 7.5.0.9 FP009, 7.5.1, and 7.6.0 before 7.6.0.2 IFIX001 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 have a default administrator account, which makes it easier for remote authenticated users to obtain access via unspecified vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IBM Maximo Asset Management contains a default administrator account with static credentials that persists across affected versions (7.1-7.1.1.13, 7.5.0 before 7.5.0.9 FP009, 7.6.0 before 7.6.0.2 IFIX001). This allows remote authenticated users to leverage this known account to obtain elevated or unauthorized access to the system beyond what their legitimate credentials would normally provide.

MitigationImmediately change or disable the default administrator account credentials, apply the vendor-supplied patches (7.5.0.9 FP009 or 7.6.0.2 IFIX001), and verify that access controls enforce proper authentication for all administrative functions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Change And Configuration Management DatabaseDatabase / datastore
Affected:= 7.1= 7.2
Maximo Asset ManagementApplication
Affected:= 7.1= 7.1.1= 7.1.1.1= 7.1.1.2= 7.1.1.5= 7.1.1.6= 7.1.1.7= 7.1.1.8= 7.1.1.9= 7.1.1.10= 7.1.1.11= 7.1.1.12
Maximo For GovernmentApplication
Affected:= 7.1= 7.5.0.0= 7.5.0.1= 7.5.0.2= 7.5.0.3= 7.5.0.4= 7.5.0.5= 7.5.0.6
Maximo For Life SciencesApplication
Affected:= 7.1= 7.5.0.0= 7.5.0.1= 7.5.0.2= 7.5.0.3= 7.5.0.4= 7.5.0.5= 7.5.0.6
Maximo For Nuclear PowerApplication
Affected:= 7.1= 7.5.0.0= 7.5.0.1= 7.5.0.2= 7.5.0.3= 7.5.0.4= 7.5.0.5= 7.5.0.6
Maximo For Oil And GasApplication
Affected:= 7.1= 7.5.0.0= 7.5.0.1= 7.5.0.2= 7.5.0.3= 7.5.0.4= 7.5.0.5= 7.5.0.6
Maximo For TransportationApplication
Affected:= 7.1= 7.5.0.0= 7.5.0.1= 7.5.0.2= 7.5.0.3= 7.5.0.4= 7.5.0.5= 7.5.0.6
Maximo For UtilitiesApplication
Affected:= 7.1= 7.5.0.0= 7.5.0.1= 7.5.0.2= 7.5.0.3= 7.5.0.4= 7.5.0.5= 7.5.0.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Maximo version
    Check the version information in the Maximo installation directory or via the Maximo About dialog (Help > About IBM Maximo Asset Management). Alternatively, query the maxversion table in the database or check the ibm/mxint properties file.
    Affected if Version is 7.1 through 7.1.1.13, 7.5.0.0 through 7.5.0.8, or 7.6.0.0 through 7.6.0.1 (before fixes)
  2. Verify if default administrator account exists
    Query the MAXUSER table in the Maximo database for the user account with userid or loginid matching the default administrative account name. Common default names include 'maxadmin' or 'mxintadm'. Run: SELECT userid, loginid, status FROM maxuser WHERE userid = 'maxadmin' or similar.
    Affected if A user account with default administrative name exists in the system
  3. Check if default account is active and enabled
    Examine the status field (or equivalent) of the default admin account in the MAXUSER table. Run: SELECT userid, status, enable FROM maxuser WHERE userid = 'maxadmin'.
    Affected if The default admin account status is active or enabled
  4. Determine if default credentials are unchanged
    Review password configuration for the default admin account. If the password is the well-known static default for this CVE, the system is vulnerable. Check whether the password matches documented default values for unpatched Maximo installations.
    Affected if The default admin account password remains at the factory default setting

If the installed version falls within 7.1-7.1.1.13, 7.5.0.0-7.5.0.8, or 7.6.0.0-7.6.0.1 AND the default administrative account exists with default credentials still active, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately change or disable the default administrator account credentials, apply the vendor-supplied patches (7.5.0.9 FP009 or 7.6.0.2 IFIX001), and verify that access controls enforce proper authentication for all administrative functions.

Fix this in Change And Configuration Management Database Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4966 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-4966 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data