dbcve.org
Rational Collaborative Lifecycle ManagementApplication · Ibm

CVE-2019-4083

MEDIUM · 5.4 CVSS v3.1 Published 2019-06-27
Fix available
A fix is available. Upgrade to after 6.0.6.1 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 Jazz Foundation products (IBM Rational Collaborative Lifecycle Management 6.0 through 6.0.6.1) is 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: 157383.

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 stored cross-site scripting (XSS) vulnerability in IBM Jazz Foundation and Rational Collaborative Lifecycle Management products versions 6.0 through 6.0.6.1. An authenticated user can embed malicious JavaScript code into the web interface, which executes when other users view the affected content, potentially exposing credentials or session tokens within a trusted session.

MitigationApply the IBM patch for this vulnerability (contact IBM support for specific fix), implement output encoding/validation on user-supplied content, and consider Content Security Policy (CSP) headers as defense-in-depth.

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:>= 6.0, <= 6.0.6.1
Rational Doors Next GenerationApplication
Affected:>= 6.0, <= 6.0.6.1
Rational Engineering Lifecycle ManagerApplication
Affected:>= 6.0, <= 6.0.6.1
Rational Quality ManagerApplication
Affected:>= 6.0, <= 6.0.6.1
Rational Rhapsody Design ManagerApplication
Affected:>= 6.0, <= 6.0.6.1
Rational Software Architect Design ManagerApplication
Affected:>= 6.0, <= 6.0.1
Rational Team ConcertApplication
Affected:>= 6.0, <= 6.0.6.1

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.1/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 the installed IBM Rational product
    Log into the Jazz Team Server web interface and navigate to the About section, or check the installation directory for the product name. Common paths: /opt/IBM/JazzTeamServer or C:\Program Files\IBM\JazzTeamServer
    Affected if Any of these products are installed: 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 the installed version number
    In the web interface, go to Server > Advanced Properties > Version, or check the installation directory for a version file. The version is typically displayed in the About dialog accessible from the main menu.
    Affected if The version cannot be determined or is not visible in the standard locations
  3. Compare your version to the affected range
    Check if your installed version falls within: 6.0 to 6.0.6.1 for most products, or 6.0 to 6.0.1 for Rational Software Architect Design Manager
    Affected if The installed version is 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4, 6.0.0.5, 6.0.0.6, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, or 6.0.6.1 (or 6.0.1 for Rational Software Architect Design Manager)
  4. Confirm the web UI is enabled
    Verify that the Jazz web interface is accessible by attempting to reach the server URL (typically https://server:9443/jts). The vulnerability requires the web interface to be available.
    Affected if The web interface is accessible and users can log in and submit content

You are affected if you have any of the listed IBM Rational products installed with a version between 6.0 and 6.0.6.1 (or 6.0.1 for Rational Software Architect Design Manager) and the web interface is enabled.

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

Apply the IBM patch for this vulnerability (contact IBM support for specific fix), implement output encoding/validation on user-supplied content, and consider Content Security Policy (CSP) headers as defense-in-depth.

Fix this in Rational Collaborative Lifecycle Management Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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