CVE-2016-9746
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 · uneditedIBM 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: 119821.
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 confidenceIBM Rational Team Concert (RTC) versions 4.0, 5.0, and 6.0 contains a cross-site scripting (XSS) vulnerability that allows users to embed arbitrary JavaScript code into the Web UI. This stored XSS could allow attackers to alter intended functionality and potentially steal credentials or session tokens within a trusted session.
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= 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= 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= 5.0.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify IBM Rational Team Concert installationLook for RTC installation directories (such as /IBM/JazzTeamServer or C:\IBM\JazzTeamServer on Windows) or check for running Jazz Team Server servicesAffected if IBM Rational Team Concert or Collaborative Lifecycle Management is installed on the system
-
Determine installed RTC versionAccess the RTC About page via the web UI (navigate to https://server:port/ccm/admin/about) or check version.xml in the installation directoryAffected if The version is 4.0.x (any 4.0, 4.0.0 through 4.0.7) or 5.0.x (5.0, 5.0.0 through 5.0.2)
-
Check if Web UI is enabledVerify the Jazz Team Server web service is running and accessible by accessing the main CCM web URL (such as https://server:port/ccm)Affected if The web interface is accessible without restrictions
-
Verify user-accessible content areas existConfirm that users can access work item, dashboard, or other areas where they can create or edit content that gets stored and displayed in the Web UIAffected if Users can submit or edit content that is rendered in the Web UI (such as work item descriptions, comments, or dashboard widgets)
A system is affected if IBM Rational Team Concert or Collaborative Lifecycle Management versions 4.0.x through 5.0.2 are installed with the Web UI accessible to users who can create or edit stored content.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor patch or upgrade to a non-vulnerable version of IBM Rational Team Concert. Additionally, implement output encoding and input validation for user-supplied content rendered in the Web UI as a defense-in-depth measure.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2016-9746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-9746 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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