dbcve.org
Maximo Asset ManagementApplication · Ibm

CVE-2015-7396

MEDIUM · 5.4 CVSS v3.0 Published 2016-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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
The Scheduler in IBM Maximo Asset Management 7.5 before 7.5.0.8 IF6 and 7.6 before 7.6.0.1 FP1 and Maximo Asset Management 7.5 before 7.5.0.8 IF6, 7.5.1, and 7.6 before 7.6.0.1 FP1 for SmartCloud Control Desk allows remote authenticated users to bypass intended access restrictions, and obtain sensitive information or modify data, 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 · moderate confidence

The vulnerability exists in the Scheduler component of IBM Maximo Asset Management and SmartCloud Control Desk. An authenticated user with standard access can bypass intended authorization controls within the Scheduler to access sensitive data they should not see or modify data they should not be able to change. The specific bypass mechanism is not detailed in available documentation.

MitigationApply IBM's patched versions: Maximo Asset Management 7.5.0.8 IF6 or later, 7.6.0.1 FP1 or later; or the corresponding SmartCloud Control Desk fixes. Verify user role mappings in the Scheduler after patching.

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
Maximo Asset ManagementApplication
Affected:= 7.5= 7.6
Maximo Asset Management EssentialsApplication
Affected:= 7.5
Maximo For GovernmentApplication
Affected:= 7.5
Maximo For Life SciencesApplication
Affected:= 7.5= 7.6
Maximo For Nuclear PowerApplication
Affected:= 7.5
Maximo For Oil And GasApplication
Affected:= 7.5
Maximo For TransportationApplication
Affected:= 7.5
Maximo For UtilitiesApplication
Affected:= 7.5

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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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. Check the installed Maximo Asset Management version
    In the Maximo application, go to the System Configuration > Platform Configuration > System Properties menu. Locate the 'version' property or check the 'maximo.version' system property. Alternatively, check the installation directory for a version file or check the IBM Installation Manager for installed packages.
    Affected if The installed version is 7.5.x (any update prior to 7.5.0.8 IF6) or 7.6.x (any update prior to 7.6.0.1 FP1)
  2. Verify if the Scheduler component is enabled
    Log into Maximo as an administrator and navigate to Administration > Resources > Roles and Permissions. Look for Scheduler-related roles or check if the Scheduler application appears in the application list. You can also check the WEB.xml deployment descriptor for scheduler-related servlet mappings.
    Affected if The Scheduler application is present and accessible in the Maximo installation
  3. Identify users with Scheduler access permissions
    In Maximo, go to Administration > Resources > Roles and Permissions. Filter for roles containing 'Scheduler' or 'SCHEDULER'. Review which security groups and roles are granted Scheduler-related permissions.
    Affected if Standard users or users with limited access are assigned Scheduler roles or permissions beyond their intended authorization level
  4. Review Scheduler data access controls
    Navigate to the Scheduler application. As a standard user (with basic privileges), attempt to view different scheduling records, work orders, or resources outside your normal scope. Check if you can view or modify records assigned to other users, departments, or organizations that should be restricted.
    Affected if A standard user can access or modify Scheduler data they were not explicitly authorized to view or edit

Your environment is affected if you are running Maximo Asset Management versions 7.5.x prior to 7.5.0.8 IF6 or 7.6.x prior to 7.6.0.1 FP1 and the Scheduler component is enabled with users assigned to it.

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

Apply IBM's patched versions: Maximo Asset Management 7.5.0.8 IF6 or later, 7.6.0.1 FP1 or later; or the corresponding SmartCloud Control Desk fixes. Verify user role mappings in the Scheduler after patching.

Fix this in Maximo Asset Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-7396 — 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-7396 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