dbcve.org
Rational Collaborative Lifecycle ManagementApplication · Ibm

CVE-2018-1762

MEDIUM · 5.4 CVSS v3.0 Published 2018-11-29
Fix available
A fix is available. Upgrade to after 6.0.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Rational Collaborative Lifecycle Management 5.0 through 5.0.2 and 6.0 through 6.0.6 are vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 148616.

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

IBM Rational Collaborative Lifecycle Management versions 5.0-5.0.2 and 6.0-6.0.6 contain a stored cross-site scripting (XSS) vulnerability in the web interface. Attackers can inject arbitrary JavaScript code that executes in the context of other users' sessions, potentially enabling credential theft or session hijacking within trusted sessions.

MitigationApply IBM's security patch for this vulnerability (contact IBM for fix availability). Implement output encoding and input validation for all user-supplied data in the web UI as a defense-in-depth measure.

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.0, <= 6.0.6
Rational Doors Next GenerationApplication
Affected:>= 5.0.0, <= 5.0.2>= 6.0.0, <= 6.0.6
Rational Engineering Lifecycle ManagerApplication
Affected:>= 5.0.0, <= 5.0.2>= 6.0.0, <= 6.0.6
Rational Quality ManagerApplication
Affected:>= 5.0.0, <= 5.0.2>= 6.0.0, <= 6.0.6
Rational Rhapsody Design ManagerApplication
Affected:>= 5.0.0, <= 5.0.2>= 6.0.0, <= 6.0.6
Rational Software Architect Design ManagerApplication
Affected:>= 5.0.0, <= 5.0.2>= 6.0.0, <= 6.0.1
Rational Team ConcertApplication
Affected:>= 5.0.0, <= 5.0.2>= 6.0.0, <= 6.0.6

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/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. Identify installed IBM Rational product
    Locate the installed IBM Rational application in your environment. Common installation paths include /opt/IBM or C:\Program Files\IBM. Check for directories such as Jazz, CLM, or product-specific folders (DOORS_Next_Generation, RationalTeamConcert, etc.)
    Affected if The product is one of: Rational Collaborative Lifecycle Management, Rational Doors Next Generation, Rational Engineering Lifecycle Manager, Rational Quality Manager, Rational Rhapsody Design Manager, Rational Software Architect Design Manager, or Rational Team Concert
  2. Determine installed version
    Check the version information for the installed product. This is typically available in the product's About section via the web UI, or in version.properties/version.txt files within the installation directory. Common locations: <install_dir>/server/etc or <install_dir>/JazzServer/configuration
    Affected if The installed version falls within 5.0.0 through 5.0.2, or 6.0.0 through 6.0.6 (exact range varies by product - see CVE details for specific product version constraints)
  3. Verify web interface accessibility
    Confirm the web-based interface is enabled and accessible. Access the application URL (typically on port 9443, 9444, or similar) and verify you can reach the login or dashboard page
    Affected if The web interface is active and reachable, as the XSS vulnerability exists in the web interface component
  4. Check for active user sessions
    Review active user sessions or recent user activity logs in the administration console. The stored XSS executes when other users view content containing the injected script
    Affected if Multiple users have access to the same web interface, as the vulnerability allows injected scripts to execute in other users' session contexts
  5. Inspect web input fields for encoding
    If you have administrative access, review the web application configuration or proxy logs to observe how user-supplied input is handled. Look for evidence of raw user input being reflected in web responses without apparent encoding
    Affected if User-supplied data appears to be rendered without proper encoding, indicating the vulnerability may be exploitable

Your environment is affected if you have any of the listed IBM Rational products installed with a version in the 5.0.x or 6.0.x range and the web interface is accessible to users.

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.6
Interim mitigation

Apply IBM's security patch for this vulnerability (contact IBM for fix availability). Implement output encoding and input validation for all user-supplied data in the web UI as a defense-in-depth measure.

Fix this in Rational Collaborative Lifecycle Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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