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

CVE-2012-2183

MEDIUM · 6.8 CVSS v2.0 Published 2012-09-10
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
Session fixation vulnerability in IBM Maximo Asset Management 6.2 through 7.5, as used in SmartCloud Control Desk, Tivoli Asset Management for IT, Tivoli Service Request Manager, Maximo Service Desk, and Change and Configuration Management Database (CCMDB), allows remote attackers to hijack web sessions 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

Session fixation vulnerability in IBM Maximo Asset Management 6.2 through 7.5 allows remote attackers to hijack web sessions by setting or predicting session IDs before authentication. The vulnerability affects multiple IBM products including SmartCloud Control Desk, Tivoli Asset Management for IT, and Tivoli Service Request Manager.

MitigationImplement proper session ID regeneration upon successful authentication and invalidate pre-login session identifiers to prevent session fixation 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
Change And Configuration Management DatabaseDatabase / datastore
Affected:= 6.0= 7.0
Maximo Asset ManagementApplication
Affected:= 6.2.0.0= 7.1.0.0= 7.5.0.0
Maximo Service DeskApplication
Affected:= 6.2
Smartcloud Control DeskApplication
Affected:= 7.0
Tivoli Asset Management For ItApplication
Affected:= 6.0= 6.2= 7.0= 7.1= 7.2
Tivoli Service Request ManagerApplication
Affected:= 7.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
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 the installed IBM product and version
    Access the Maximo or related IBM application web interface and locate the version information, typically found in the About section, System Configuration, or the login page footer. Alternatively, check installation directories or system information for the specific IBM product (Maximo Asset Management, SmartCloud Control Desk, Tivoli Asset Management for IT, or Tivoli Service Request Manager).
    Affected if The installed product matches one of the affected versions: Maximo Asset Management 6.2.x, 7.1.x, or 7.5.x; SmartCloud Control Desk 7.0; Tivoli Asset Management for IT 6.0, 6.2, 7.0, 7.1, or 7.2; or Tivoli Service Request Manager 7.0.
  2. Verify web application accessibility
    Confirm the IBM web application is accessible over HTTP/HTTPS and accepts user connections. This vulnerability is exploitable through the web interface.
    Affected if The web application is exposed and accepts connections.
  3. Test session ID behavior before authentication
    Access the login page and observe the session cookie or session ID presented by the application before entering credentials. Record the session identifier value provided by the server.
    Affected if The application assigns and exposes a session ID to unauthenticated users before login.
  4. Test session ID regeneration after authentication
    Authenticate with valid credentials and observe whether the session ID changes after successful login. Compare the session identifier before and after authentication.
    Affected if The session ID remains the same before and after authentication, indicating no session regeneration occurs.
  5. Check session configuration settings
    Examine the application server configuration (such as WebSphere or other IBM application server settings) for session management policies, specifically whether session fixation protection is enabled or whether the application is configured to regenerate session IDs upon login.
    Affected if Session fixation protection is disabled or the configuration allows session IDs to be set/predetermined before authentication.

The environment is affected if the installed IBM product version falls within the listed affected versions AND the application does not regenerate session IDs after successful authentication, allowing an attacker to set or predict the session ID before login.

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 proper session ID regeneration upon successful authentication and invalidate pre-login session identifiers to prevent session fixation attacks.

Fix this in Change And Configuration Management Database Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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