dbcve.org
Rational Quality ManagerApplication · Ibm

CVE-2017-1293

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

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

Stored cross-site scripting (XSS) vulnerability in IBM Rational Quality Manager and IBM Rational Collaborative Lifecycle Management allows authenticated users to inject malicious JavaScript into the web interface. When other users view the compromised content, the embedded script executes within their trusted session, potentially enabling session hijacking and credential disclosure.

MitigationApply IBM security patches for versions 5.0 through 5.0.2 and 6.0 through 6.0.5 as specified in IBM's security bulletin. Implement input validation and output encoding as defense-in-depth measures until patches are 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 IBM Rational product
    Locate IBM Rational Quality Manager or IBM Rational Collaborative Lifecycle Management installations in your environment. Check for associated services, directories, or applications bearing these product names.
    Affected if Either IBM Rational Quality Manager or IBM Rational Collaborative Lifecycle Management is present in the environment
  2. Determine installed version of IBM Rational Quality Manager
    Access the product administration interface or use the product's about/version information panel. Typical paths include the application header menu or admin settings. Query the application for its exact version number.
    Affected if Version equals 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
  3. Determine installed version of IBM Rational Collaborative Lifecycle Management
    Access the CLM administration console or about page. Query the application for its exact version number, typically found in the header or system information section.
    Affected if Version equals 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
  4. Verify web interface is accessible
    Confirm the IBM Rational web interface is accessible and active. Test connectivity to the application URL.
    Affected if The web interface is reachable and users can authenticate to the application

A user is affected if IBM Rational Quality Manager or IBM Rational Collaborative Lifecycle Management is installed with version 5.0.0 through 5.0.2 or 6.0.0 through 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 security patches for versions 5.0 through 5.0.2 and 6.0 through 6.0.5 as specified in IBM's security bulletin. Implement input validation and output encoding as defense-in-depth measures until patches are deployed.

Fix this in Rational Quality Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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