dbcve.org
Rational Team ConcertApplication · Ibm

CVE-2017-1113

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 Rational Team Concert (RTC) 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: 121151.

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

A stored cross-site scripting (XSS) vulnerability in IBM Rational Team Concert versions 4.0, 5.0, and 6.0 allows authenticated users to embed arbitrary JavaScript code into the Web UI through unsanitized input fields. This malicious script executes within the context of other users' trusted sessions, potentially enabling credential theft or session hijacking.

MitigationUpgrade IBM Rational Team Concert to the latest patched version as specified in IBM's security bulletin. Implement output encoding and input validation on all user-supplied data fields as a defense-in-depth measure until the upgrade is completed.

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

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 the installed IBM Rational Team Concert version
    Log into the Jazz Team Server administration interface and navigate to the About section, or use the CCM web URL with /admin?internal=true to view server diagnostics. The version is typically displayed on the login page footer or in the server info page.
    Affected if The installed version is 4.0.x, 5.0.x, or 6.0.x (any subversion within these major releases). Compare your version against these ranges.
  2. Confirm the Web UI is enabled and accessible
    Verify that the Rational Team Concert web client interface is accessible by navigating to your CCM server URL (typically https://server:port/ccm/web). The vulnerability exists in the Web UI component.
    Affected if The Web UI is publicly or internally accessible without restriction.
  3. Determine if external or untrusted users can authenticate
    Review the user authentication configuration in the Jazz Team Server administration console under User Management. Check whether external users, non-employees, or users from untrusted domains can create accounts or log in.
    Affected if Authenticated users outside the trusted internal user base can access the system.
  4. Inspect input fields in the Web UI for sanitization
    As an authenticated user, attempt to enter HTML or JavaScript characters (such as <script>alert(1)</script> or <img src=x onerror=alert(1)>) into common text fields like work item descriptions, comments, or user profile fields. Submit the form and view the stored content.
    Affected if The input is stored and rendered without encoding or sanitization, meaning the raw HTML/JavaScript executes when viewed by other users.

You are affected if your IBM Rational Team Concert version falls within 4.0.x, 5.0.x, or 6.0.x AND the Web UI is accessible to authenticated users who can input data into unsanitized fields.

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

Upgrade IBM Rational Team Concert to the latest patched version as specified in IBM's security bulletin. Implement output encoding and input validation on all user-supplied data fields as a defense-in-depth measure until the upgrade is completed.

Fix this in Rational Team Concert Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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