dbcve.org
Rational Quality ManagerApplication · Ibm

CVE-2017-1275

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: 124750.

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 Cross-Site Scripting (XSS) vulnerability in IBM Rational Quality Manager and IBM Rational Collaborative Lifecycle Management versions 5.0-5.0.2 and 6.0-6.0.5. The flaw allows authenticated users to embed malicious JavaScript code into Web UI input fields, which then executes in the browsers of other users viewing the injected content, potentially enabling session hijacking and credential theft within trusted sessions.

MitigationApply IBM's official security patches for this vulnerability (contact IBM Support for fix packages). Implement output encoding and Content Security Policy (CSP) headers as defense-in-depth measures until patches can be deployed.

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:= 5.0.0= 5.0.1= 5.0.2= 6.0.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5
Rational Collaborative Lifecycle ManagementApplication
Affected:= 5.0.0= 5.0.1= 5.0.2= 6.0.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 installed product and version
    Locate the installed version of IBM Rational Quality Manager or IBM Rational Collaborative Lifecycle Management in the product's about panel, installation directory, or admin console. This is typically found in the application header under Help > About or in the installation logs.
    Affected if The installed version is any of: 5.0.0, 5.0.1, 5.0.2, 6.0.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, or 6.0.5
  2. Verify Web UI accessibility
    Confirm that the web-based user interface is accessible and operational. Access the application URL and verify normal login and navigation functions work.
    Affected if The Web UI is accessible and users can log in to the application
  3. Confirm user authentication is enabled
    Check that user authentication is enabled and users can authenticate to the Rational Quality Manager or CLM web interface.
    Affected if Authenticated users can access input fields in the Web UI
  4. Check for malicious script injection in input fields
    Inspect web application input fields (such as text fields, description fields, or comment areas) for unexpected script tags or JavaScript code. Use browser developer tools or proxy to examine stored content.
    Affected if Input fields accept and store unescaped HTML or JavaScript content that executes when viewed by other users

Your environment is affected if you are running any version of IBM Rational Quality Manager or IBM Rational Collaborative Lifecycle Management between 5.0 and 5.0.2 or between 6.0 and 6.0.5, and the web interface is accessible to authenticated users.

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 official security patches for this vulnerability (contact IBM Support for fix packages). Implement output encoding and Content Security Policy (CSP) headers as defense-in-depth measures until patches can be deployed.

Fix this in Rational Quality Manager 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-1275 — 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-1275 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