dbcve.org
Maximo Asset ManagementApplication · Ibm

CVE-2012-6356

MEDIUM · 6.5 CVSS v2.0 Published 2013-02-20
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.5, Maximo Asset Management Essentials 7.5, and SmartCloud Control Desk 7.5 allow remote authenticated users to gain privileges via vectors related to an import operation.

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

This vulnerability in IBM Maximo Asset Management 7.5 and related products allows remote authenticated users to gain elevated privileges through the import functionality. The specific weakness in the import operation permits privilege escalation beyond what the user's normal permissions should allow.

MitigationApply the IBM fix pack for this vulnerability, restrict import functionality to only necessary users, implement least-privilege access controls for import operations, and audit import activity logs.

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.0.0
Maximo Asset Management EssentialsApplication
Affected:= 7.5.0.0
Smartcloud Control DeskApplication
Affected:= 7.5.0.0

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 the installed Maximo version
    Access the Maximo System Information dialog (System Configuration > Platform Configuration > System Information) or check the maxversion property in the maximo.ear file metadata. Alternatively, query the database: SELECT version FROM maxversion;
    Affected if The installed version is exactly 7.5.0.0 for Maximo Asset Management, Maximo Asset Management Essentials, or Smartcloud Control Desk
  2. Verify if import functionality is enabled
    Navigate to Administration > System Configuration > Platform Configuration > Application Designer. Locate the import feature (typically under File > Import or the Import button in object-based applications). Check whether the import applications or modules are deployed and accessible in the Maximo web interface.
    Affected if The import functionality is deployed and accessible to users in the environment
  3. Confirm user access to import operations
    Log in as a standard (non-admin) user and navigate to the Import functionality. Attempt to access import features in applications like Quick Flow Import, Excel Import, or the Integration Module import capabilities. Check the Security Groups and Permissions to see which groups have Import access.
    Affected if Standard or low-privilege users have access to import operations that should be restricted
  4. Inspect import-related security permissions
    In Maximo, go to Security > Groups (or Roles) and examine which groups are granted Import/Export permissions (object-level security for MXIMPORT, MXEXPORT objects). Check if any group with limited privileges has been granted import access to sensitive objects.
    Affected if Users with limited roles have been granted import permissions that could allow privilege escalation

You are affected if your environment runs Maximo Asset Management, Maximo Asset Management Essentials, or Smartcloud Control Desk version 7.5.0.0 AND the import functionality is accessible to users who should not have elevated privileges.

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 the IBM fix pack for this vulnerability, restrict import functionality to only necessary users, implement least-privilege access controls for import operations, and audit import activity logs.

Fix this in Maximo Asset Management Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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