dbcve.org
Rational Quality ManagerApplication · Ibm

CVE-2016-2864

MEDIUM · 5.4 CVSS v3.0 Published 2016-11-24
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
Cross-site scripting (XSS) vulnerability in IBM Rational Collaborative Lifecycle Management 3.0.1.6 before iFix8, 4.0 before 4.0.7 iFix11, 5.0 before 5.0.2 iFix18, and 6.0 before 6.0.2 iFix5; Rational Quality Manager 3.0.1.6 before iFix8, 4.0 before 4.0.7 iFix11, 5.0 before 5.0.2 iFix18, and 6.0 before 6.0.2 iFix5; Rational Team Concert 3.0.1.6 before iFix8, 4.0 before 4.0.7 iFix11, 5.0 before 5.0.2 iFix18, and 6.0 before 6.0.2 iFix5; Rational DOORS Next Generation 4.0 before 4.0.7 iFix11, 5.0 before 5.0.2 iFix18, and 6.0 before 6.0.2 iFix5; Rational Engineering Lifecycle Manager 4.x before 4.0.7 iFix11, 5.0 before 5.0.2 iFix18, and 6.0 before 6.0.2 iFix5; Rational Rhapsody Design Manager 4.0 before 4.0.7 iFix11, 5.0 before 5.0.2 iFix18, and 6.0 before 6.0.2 iFix5; and Rational Software Architect Design Manager 4.0 before 4.0.7 iFix11, 5.0 before 5.0.2 iFix18, and 6.0 before 6.0.2 iFix5 allows remote authenticated users to inject arbitrary web script or HTML via a crafted URL.

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

Cross-site scripting (XSS) vulnerability in IBM Rational Collaborative Lifecycle Management and related products allows authenticated users to inject arbitrary web script or HTML via crafted URLs. The vulnerability exists in multiple product versions (3.0.1.6 through 6.0.x) before specific iFix levels.

MitigationApply vendor-supplied iFix patches (iFix8 for 3.0.1.6, iFix11 for 4.0.x, iFix18 for 5.0.x, iFix5 for 6.0.x) to all affected IBM Rational products, and implement output encoding and input validation 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 Quality ManagerApplication
Affected:= 3.0.1.6= 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.0= 5.0.1= 5.0.2
Rational Engineering Lifecycle ManagerApplication
Affected:= 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.0= 5.0.1= 5.0.2= 6.0.0
Rational Team ConcertApplication
Affected:= 3.0.1.6= 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.0= 5.0.1= 5.0.2
Rational Collaborative Lifecycle ManagementApplication
Affected:= 3.0.1.6= 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.0= 5.0.1= 5.0.2
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.0= 5.0.1= 5.0.2= 6.0.0
Rational Doors Next GenerationApplication
Affected:= 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.0= 5.0.1= 5.0.2= 6.0.0
Rational Software Architect Design ManagerApplication
Affected:= 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.0= 5.0.1= 5.0.2= 6.0.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 installed IBM Rational product
    Check the application name in the web browser URL or the product startup logs. Common paths include /qm for Quality Manager, /ccm for Team Concert, /dng for Doors Next Generation, /relm for Engineering Lifecycle Manager, /rdm for Rhapsody Design Manager, /rsadm for Software Architect Design Manager.
    Affected if The product name matches any of the affected products: Rational Quality Manager, Rational Engineering Lifecycle Manager, Rational Team Concert, Rational Collaborative Lifecycle Management, Rational Rhapsody Design Manager, Rational Doors Next Generation, or Rational Software Architect Design Manager
  2. Determine installed product version
    Access the About section in the product web interface (typically via Help > About) or check the installation directory for version.info or similar version file. The version is also visible in the footer of the web application login page.
    Affected if The installed version matches 3.0.1.6, 4.0.0 through 4.0.7, 5.0.0 through 5.0.2, or 6.0.0 for any of the affected products.
  3. Check if web interface is accessible
    Attempt to access the product URL in a web browser. For example, https://server:port/qm, https://server:port/ccm, https://server:port/dng, or similar product-specific paths.
    Affected if The web interface responds and displays a login or application page, indicating the web component is enabled.
  4. Verify authentication is configured
    Confirm that user authentication is enabled by attempting to log in or checking the administration security settings in the web interface.
    Affected if Users can authenticate to the application, as the vulnerability requires an authenticated user session to exploit the XSS.

If the installed IBM Rational product version falls within 3.0.1.6 through 6.0.x and the web interface with authentication is accessible, the environment is likely affected by this XSS vulnerability.

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 vendor-supplied iFix patches (iFix8 for 3.0.1.6, iFix11 for 4.0.x, iFix18 for 5.0.x, iFix5 for 6.0.x) to all affected IBM Rational products, and implement output encoding and input validation as defense-in-depth.

Fix this in Rational Quality Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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