dbcve.org
Rational Collaborative Lifecycle ManagementApplication · Ibm

CVE-2016-9973

MEDIUM · 5.4 CVSS v3.0 Published 2017-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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 Jazz Foundation 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: 120209.

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 Jazz Foundation contains a stored cross-site scripting (XSS) vulnerability in its Web UI. Attackers can embed arbitrary JavaScript code into web interfaces, which executes when other users view the injected content, potentially leading to session hijacking and credential disclosure within trusted sessions.

MitigationApply IBM patches for Jazz Foundation (contact IBM support for applicable fix packs). Implement output encoding for user-supplied content and configure Content-Security-Policy headers to mitigate XSS execution.

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:= 4.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0= 5.0.1= 5.0.2= 6.0
Rational Quality ManagerApplication
Affected:= 4.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0= 5.0.1= 5.0.2= 6.0
Rational Team ConcertApplication
Affected:= 4.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0= 5.0.1= 5.0.2= 6.0
Rational Doors Next GenerationApplication
Affected:= 4.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0= 5.0.1= 5.0.2= 6.0
Rational Engineering Lifecycle ManagerApplication
Affected:= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0= 5.0.1= 5.0.2= 6.0= 6.0.1= 6.0.2= 6.0.3
Rational Rhapsody Design ManagerApplication
Affected:= 4.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0= 5.0.1= 5.0.2= 6.0
Rational Software Architect Design ManagerApplication
Affected:= 4.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0= 5.0.1= 5.0.2= 6.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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/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
    Access the Jazz Administration interface or check the installation directory for the product name. Look at the application server or the installed applications list.
    Affected if The product is one of: Rational Collaborative Lifecycle Management, Rational Quality Manager, Rational Team Concert, Rational Doors Next Generation, Rational Engineering Lifecycle Manager, Rational Rhapsody Design Manager, or Rational Software Architect Design Manager
  2. Determine the installed product version
    In the Jazz Administration console, go to the 'About' or 'Version' section. Alternatively, check the installation logs or the server startup output for the exact version number.
    Affected if The version matches any of: 4.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 5.0, 5.0.1, 5.0.2, 6.0, 6.0.1, 6.0.2, or 6.0.3 (depending on product)
  3. Verify the Web UI is accessible
    Attempt to access the web interface of the Jazz application through a browser. Check if the /jazz or similar web endpoints respond.
    Affected if The Web UI is exposed and users can submit content to be stored and displayed (such as comments, descriptions, or artifacts)
  4. Review user input fields in the Web UI
    Log into the Web UI as a standard user and identify fields that accept and store user-supplied text for later display (e.g., artifact comments, description fields, requirement text).
    Affected if The application stores and displays user-supplied content without visible output encoding

You are affected if your installed IBM Rational product version matches one of the affected versions listed and the Web UI is accessible to users who can submit and view stored content.

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 IBM patches for Jazz Foundation (contact IBM support for applicable fix packs). Implement output encoding for user-supplied content and configure Content-Security-Policy headers to mitigate XSS execution.

Fix this in Rational Collaborative Lifecycle Management Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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