dbcve.org
Rational Collaborative Lifecycle ManagementApplication · Ibm

CVE-2017-1312

MEDIUM · 5.4 CVSS v3.0 Published 2018-07-03
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 Quality Manager and IBM Rational Collaborative Lifecycle Management 5.0 through 5.0.2 and 6.0 through 6.0.5 are 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: 125723.

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

This is a stored (persistent) cross-site scripting (XSS) vulnerability in IBM Rational Quality Manager and IBM Rational Collaborative Lifecycle Management. The flaw allows authenticated users to embed malicious JavaScript code into the Web UI, which executes when other users view the affected content, potentially enabling session hijacking and credentials disclosure.

MitigationApply IBM's security patches for this vulnerability (contact IBM support for fix availability) and implement output encoding for user-supplied content to prevent 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:= 5.0= 5.0.1= 5.0.2= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5
Rational Quality ManagerApplication
Affected:= 5.0= 5.0.1= 5.0.2= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5

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 product
    Locate the IBM Rational application and determine whether it is Rational Quality Manager (RQM) or Rational Collaborative Lifecycle Management (CLM). Check the application's About or version information page, or consult the installation inventory documentation.
    Affected if The installed product is RQM or CLM with version 5.0.x or 6.0.x through 6.0.5
  2. Verify the exact version number
    Access the product version information through the administrative console or by querying the installation directory for version metadata. Compare the installed version against the list: 5.0, 5.0.1, 5.0.2, 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, or 6.0.5.
    Affected if The installed version exactly matches any of the versions listed in the affected range
  3. Confirm the Web UI is enabled
    Verify that the Rational QM or CLM web interface is accessible and active. Check the application server configuration to ensure the web-based user interface component is running.
    Affected if The Web UI is exposed and users can log in to submit or view content
  4. Check for user input fields in the Web UI
    Log into the web interface as a standard authenticated user and identify areas where content can be submitted, such as test artifacts, comments, requirements, or document attachments.
    Affected if User-controllable input fields exist in the web interface where content can be stored and displayed to other users
  5. Assess authentication and access controls
    Review the user authentication configuration to determine whether multiple user roles exist and whether untrusted or external users have access to view content submitted by other users.
    Affected if The system allows authenticated users to submit content that is viewable by other users without sufficient output encoding

Your environment is affected if you are running IBM Rational Quality Manager or Collaborative Lifecycle Management versions 5.0 through 6.0.5 with the Web UI enabled and users can submit and view content from each other.

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's security patches for this vulnerability (contact IBM support for fix availability) and implement output encoding for user-supplied content to prevent XSS execution.

Fix this in Rational Collaborative Lifecycle Management Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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