CVE-2017-1655
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 · uneditedIBM Jazz Foundation (IBM Rational Collaborative Lifecycle Management 5.0 and 6.0) is 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: 133379.
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 confidenceStored cross-site scripting (XSS) vulnerability in IBM Jazz Foundation components used by IBM Rational Collaborative Lifecycle Management 5.0 and 6.0. Attackers can inject malicious JavaScript code through web UI inputs that persists on the server and executes in the browsers of other users viewing the affected content, potentially exfiltrating session credentials or performing actions on behalf of authenticated users.
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>= 4.0, <= 6.0.5>= 4.0, <= 4.0.7>= 5.0, <= 5.0.2>= 6.0, <= 6.0.5>= 4.0, <= 4.0.7>= 5.0, <= 5.0.2>= 6.0, <= 6.0.5>= 4.0.1, <= 4.0.7>= 5.0, <= 5.0.2>= 6.0.0, <= 6.0.5>= 4.0.3, <= 4.0.7>= 5.0, <= 5.0.2>= 6.0, <= 6.0.5>= 4.0, <= 4.0.7>= 5.0, <= 5.0.2>= 6.0, <= 6.0.5>= 4.0, <= 4.0.7>= 5.0, <= 5.0.2> 6.0, <= 6.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Rational CLM productDetermine which IBM Rational product is running in your environment (Rational Collaborative Lifecycle Management, Rational Quality Manager, Rational Team Concert, Rational Doors Next Generation, Rational Engineering Lifecycle Manager, Rational Rhapsody Design Manager, or Rational Software Architect Design Manager)Affected if Any of these products are installed and the version falls within the affected ranges
-
Determine the installed version numberAccess the product's about or version information panel in the web UI, or use the administration console to view the installed versionAffected if The installed version matches one of the vulnerable ranges: 4.0 through 4.0.7, 5.0 through 5.0.2, 6.0 through 6.0.5, or for Rational Software Architect Design Manager specifically 6.0.1 and below
-
Confirm web UI is accessibleVerify that the Jazz web interface is accessible to users (typically at /jts, /ccm, /qm, /rm, or /relm endpoints)Affected if The web UI is enabled and accessible to users, providing input fields where malicious JavaScript could be injected and persisted
-
Check for existing XSS payloadsReview server logs and application data for suspicious script tags or JavaScript fragments in user-contributed fields such as comments, descriptions, or metadataAffected if Malicious script content is found stored in the database, indicating exploitation has occurred
You are affected if any IBM Rational CLM product listed is installed with a version between 4.0 and 6.0.5 (or 6.0.1 for Rational Software Architect Design Manager) and the web UI is accessible to users.
Generated from the published advisory. Verify against your own configuration.
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 dataApply IBM's patches for affected versions (5.0.x and 6.0.x) per IBM X-Force ID 133379. Additionally, implement output encoding, input validation, and Content Security Policy headers to mitigate XSS vectors.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1655 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-1655 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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