dbcve.org
Rational Team ConcertApplication · Ibm

CVE-2016-9701

MEDIUM · 5.4 CVSS v3.0 Published 2017-07-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Team Concert 4.0, 5.0 and 6.0 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: 119529.

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 Team Concert versions 4.0, 5.0, and 6.0 contain a cross-site scripting vulnerability in the web interface. Attackers can embed arbitrary JavaScript code through user-supplied input, which executes in the browsers of other users viewing the affected content, potentially exposing session credentials or cookies.

MitigationApply the vendor patch or upgrade to a patched version of IBM Team Concert. Additionally, implement output encoding and input validation on user-supplied data in the web interface.

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 Team ConcertApplication
Affected:= 4.0= 4.0.0= 4.0.0.1= 4.0.0.2= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0
Rational Collaborative Lifecycle ManagementApplication
Affected:= 4.0= 4.0.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.0= 5.0.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.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 Team Concert version
    Access the Jazz Team Server administration console or check the installation directory for the version.xml or about.html file. The version is typically displayed on the 'About' page of the Jazz Team Server web interface at /jts/about
    Affected if The installed version matches 4.0.x, 5.0.x, or 6.0.x (any version from 4.0 through 5.0.7 or 6.0)
  2. Identify installed IBM Rational Collaborative Lifecycle Management version
    Check the installation for CLM version by accessing the About page of any CLM application (JTS, CCM, QM, RM) or check the version.txt in the installation root directory
    Affected if The installed version matches 4.0.x through 5.0.1 (any version from 4.0 through 5.0.1)
  3. Verify web interface is accessible
    Confirm the Jazz Team Server or CLM web interface is reachable over HTTP/HTTPS. Try accessing the login page of the deployment
    Affected if The web interface is exposed and accessible to users or attackers
  4. Confirm user input fields exist in web interface
    Log into the web interface and navigate to areas where user-generated content can be submitted, such as work item descriptions, comments, or project dashboards
    Affected if The web interface accepts user-supplied input that could be rendered without proper encoding
  5. Compare version against CVE affected ranges
    If the exact version cannot be determined, check the product release notes or installed fixes via the IBM Installation Manager
    Affected if The installed version falls within 4.0, 4.0.0.x, 4.0.1.x, 4.0.2.x, 4.0.3.x, 4.0.4.x, 4.0.5.x, 4.0.6.x, 4.0.7, 5.0, 5.0.0.x, 5.0.1, or 6.0 for Team Concert; or 4.0.x through 5.0.1 for CLM

The environment is affected if IBM Rational Team Concert version 4.0.x/5.0.x/6.0.x or IBM Rational Collaborative Lifecycle Management version 4.0.x through 5.0.1 is installed and the web interface is accessible.

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 the vendor patch or upgrade to a patched version of IBM Team Concert. Additionally, implement output encoding and input validation on user-supplied data in the web interface.

Fix this in Rational Team Concert Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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