dbcve.org
Maximo Asset ManagementApplication · Ibm

CVE-2011-1397

MEDIUM · 6.8 CVSS v2.0 Published 2012-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges 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
Cross-site request forgery (CSRF) vulnerability in the Labor Reporting page in IBM Maximo Asset Management and Asset Management Essentials 6.2, 7.1, and 7.5; IBM Tivoli Asset Management for IT 6.2, 7.1, and 7.2; IBM Tivoli Service Request Manager 7.1 and 7.2; IBM Maximo Service Desk 6.2; and IBM Tivoli Change and Configuration Management Database (CCMDB) 6.2, 7.1, and 7.2 allows remote attackers to hijack the authentication of arbitrary users.

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

Cross-site request forgery (CSRF) vulnerability in the Labor Reporting page of IBM Maximo Asset Management and related products allows remote attackers to hijack the authentication of arbitrary users by tricking authenticated users into submitting malicious requests.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on the Labor Reporting page and all state-changing operations, and configure session cookies with SameSite attributes to prevent cross-site request forgery attacks.

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:= 6.2= 7.1= 7.5
Maximo Asset Management EssentialsApplication
Affected:= 6.2= 7.1= 7.5
Tivoli Asset Management For ItApplication
Affected:= 6.2= 7.1= 7.2
Trivoli Service Request ManagerApplication
Affected:= 7.1= 7.2
Maximo Service DeskApplication
Affected:= 6.2
Tivoli Change And Configuration Management DatabaseDatabase / datastore
Affected:= 6.2= 7.1= 7.2

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/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 product and version
    Access the Maximo system and navigate to the System Configuration > Platform Configuration > System Properties menu, or check the 'maxversion.properties' or 'build.level' file in the installation directory. Alternatively, log into Maximo and go to Help > About to view the version information.
    Affected if The installed product is one of: Maximo Asset Management, Maximo Asset Management Essentials, Tivoli Asset Management For IT, Trivoli Service Request Manager, Maximo Service Desk, or Tivoli Change And Configuration Management Database AND the version is 6.2, 7.1, 7.2, or 7.5.
  2. Verify Labor Reporting page is accessible
    Navigate to the Labor Reporting module in the Maximo interface. This is typically found under the Modules menu as 'Labor Reporting' or 'Report Labor'. Try to access a Labor Reporting entry form to confirm the functionality exists in the deployment.
    Affected if The Labor Reporting page is present and accessible to users in the environment.
  3. Inspect Labor Reporting page for anti-CSRF tokens
    Open the Labor Reporting page in a browser, view the page source (right-click > View Page Source), and search for hidden form fields containing tokens, anti-CSRF parameters, or synchronization tokens. Also use browser developer tools to examine form submissions for any token-based protection in POST requests.
    Affected if No anti-CSRF token, synchronizer token, or unique request identifier is found in the HTML source of the Labor Reporting page forms.
  4. Check session cookie configuration
    Using browser developer tools (Application tab > Cookies), inspect the session cookies for the Maximo application. Look for the 'SameSite' attribute on cookies, or check the underlying configuration files (web.xml, ibm-web-ext.xmi) for SameSite cookie settings.
    Affected if Session cookies do not have the SameSite attribute set, or the SameSite attribute is set to 'None' without Secure flag.

A user is affected if they are running any of the listed IBM products at versions 6.2, 7.1, 7.2, or 7.5 with the Labor Reporting page accessible and without proper anti-CSRF token protection on that page.

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

Implement anti-CSRF tokens (synchronizer token pattern) on the Labor Reporting page and all state-changing operations, and configure session cookies with SameSite attributes to prevent cross-site request forgery attacks.

Fix this in Maximo Asset Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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