dbcve.org
Rational Quality ManagerApplication · Ibm

CVE-2017-1277

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

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

IBM Rational Quality Manager and IBM Rational Collaborative Lifecycle Management versions 5.0-5.0.2 and 6.0-6.0.5 contain a stored or reflected cross-site scripting vulnerability in the Web UI. Attackers can embed arbitrary JavaScript code through user-supplied input, which executes in the context of other users' sessions, potentially allowing credential theft via cookie/session hijacking within a trusted session.

MitigationApply IBM security patches for this vulnerability. Implement input validation and output encoding for all user-supplied data in the Web UI layer 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 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 the installed IBM Rational product
    Access the application server admin console or check the installed applications. Look for either 'IBM Rational Quality Manager' or 'IBM Rational Collaborative Lifecycle Management' in the installed software list.
    Affected if The product is either IBM Rational Quality Manager or IBM Rational Collaborative Lifecycle Management
  2. Determine the installed product version
    In the Web UI, go to the About section (usually via the user menu > About) or check the installation directory for a version file. The exact version number will be displayed (for example, 5.0.1, 6.0.4).
    Affected if The version matches exactly 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. Confirm the Web UI is enabled
    Attempt to access the web interface via the standard URL pattern (for example, https://server:port/rm, https://server:port/jts). The vulnerability exists in the Web UI layer, so the UI must be accessible for exploitation.
    Affected if The Web UI is accessible and responsive to user input
  4. Verify user-supplied input handling in the Web UI
    Review Web UI configuration files in the application server directory for input validation settings. Check if custom scripts or forms in the UI accept user input that could be reflected back without encoding.
    Affected if The Web UI accepts user input without sanitization or the input validation configuration is missing or disabled

The environment is affected if either IBM Rational Quality Manager or IBM Rational Collaborative Lifecycle Management is installed with a version matching 5.0.0 through 5.0.2 or 6.0.0 through 6.0.5, and the Web UI is accessible to 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 this vulnerability. Implement input validation and output encoding for all user-supplied data in the Web UI layer to prevent XSS execution.

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