dbcve.org
Rational Collaborative Lifecycle ManagementApplication · Ibm

CVE-2018-1492

MEDIUM · 6.8 CVSS v3.0 Published 2018-07-10
Fix available
A fix is available. Upgrade to after 6.0.5 or later.
See remediation →
73/100
Remediation priority · Elevated
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
IBM Jazz Foundation products could allow a user with physical access to the system to log in as another user due to the server's failure to properly log out from the previous session. IBM X-Force ID: 140977.

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 is a session management vulnerability in IBM Jazz Foundation products where the server fails to properly invalidate user sessions after logout. A user with physical access to an unattended workstation can access the previous user's session without authentication credentials.

MitigationImplement proper server-side session invalidation on logout, enforce session timeouts, and ensure session cookies are invalidated upon logout. Consider additional authentication factors for sensitive operations.

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
Rational Collaborative Lifecycle ManagementApplication
Affected:>= 5.0, <= 6.0.5
Rational Team ConcertApplication
Affected:>= 5.0, <= 5.0.2>= 6.0.0, <= 6.0.5
Rational Doors Next GenerationApplication
Affected:>= 5.0, <= 5.0.2>= 6.0.0, <= 6.0.5
Rational Quality ManagerApplication
Affected:>= 5.0, <= 5.0.2>= 6.0.0, <= 6.0.5
Rational Rhapsody Design ManagerApplication
Affected:>= 5.0, <= 5.0.2>= 6.0.0, <= 6.0.5
Rational Software Architect Design ManagerApplication
Affected:>= 5.0, <= 5.0.2>= 6.0, <= 6.0.1
Rational Engineering Lifecycle ManagerApplication
Affected:>= 5.0, <= 5.0.2>= 6.0.0, <= 6.0.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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 IBM Jazz product and version
    Locate the installation directory for the IBM Rational application (commonly in /opt/IBM or C:\Program Files\IBM). Check the About section in the application UI, or look for version files in the installation folder (often in a jazz\About or similar directory). The server may also expose version information via the /ccm/web/upgradeStatus or /jts/web/infostream service endpoints.
    Affected if The installed product is one of: Rational Collaborative Lifecycle Management, Rational Team Concert, Rational Doors Next Generation, Rational Quality Manager, Rational Rhapsody Design Manager, Rational Software Architect Design Manager, or Rational Engineering Lifecycle Manager, AND the version fall
  2. Confirm session cookie persists after logout
    Log into the application as a test user. Capture the session cookie (typically named JazzAuth or similar in the jts/ccm domains). Perform a logout action. Attempt to re-use the captured cookie value in subsequent HTTP requests to authenticated endpoints without re-authenticating.
    Affected if The session cookie remains valid and authenticated after logout is completed - the server accepts requests with the old cookie without requiring new credentials.
  3. Check server session timeout configuration
    Access the IBM Jazz administration console (typically at /jts/admin). Navigate to Server > Advanced Properties. Look for session timeout settings such as 'session.timeout.minutes' or similar session lifecycle parameters.
    Affected if Session timeout is set to an excessively long duration (24+ hours) or is disabled entirely, or if no server-side session invalidation occurs on logout.

Your environment is affected if you run any of the listed IBM Jazz products within versions 5.0 through 6.0.5 and sessions remain usable after logout.

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
Upgrade available Upgrade to a release after 6.0.5
Interim mitigation

Implement proper server-side session invalidation on logout, enforce session timeouts, and ensure session cookies are invalidated upon logout. Consider additional authentication factors for sensitive operations.

Fix this in Rational Collaborative Lifecycle 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 the upgrade done

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-2018-1492 — 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-2018-1492 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