dbcve.org
Rational Collaborative Lifecycle ManagementApplication · Ibm

CVE-2017-1169

MEDIUM · 5.4 CVSS v3.0 Published 2017-10-25
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 DOORS next Generation (DNG/RRC) 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: 123188.

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 · moderate confidence

IBM DOORS Next Generation (DNG/RRC) contains a stored cross-site scripting (XSS) vulnerability in its Web UI. Attackers can embed arbitrary JavaScript code through user inputs that are not properly sanitized, allowing execution within the context of other users' trusted sessions and potentially leading to credential theft.

MitigationApply IBM's patch for this vulnerability (contact IBM support for specific fix). Additionally, implement input validation and output encoding on all user-supplied data, and configure Content Security Policy (CSP) headers to mitigate 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:= 4.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 5.0= 5.0.1= 5.0.2= 6.0

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 IBM DOORS Next Generation installation
    Check for IBM Rational DOORS Next Generation (DNG) or Rational Requirements Composer (RRC) installation on the system. Look in standard IBM installation directories (e.g., /opt/IBM, C:\IBM\) or check the Windows Programs and Features list for IBM Rational CLM components.
    Affected if The software is present on the system
  2. Determine installed CLM version
    Access the IBM Jazz Team Server administrative console (typically at https://server:9443/ccm/admin) and navigate to the Server > Advanced Properties page, or check the installation manifest files in the installation directory for the version number.
    Affected if The installed version is 4.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 5.0, 5.0.1, 5.0.2, or 6.0
  3. Verify Web UI is enabled
    Confirm the DOORS Next Generation Web UI is accessible. Try accessing the application through a web browser at the standard URLs (such as /rm or /doorsNG). Check in the Jazz Team Server admin console that the Requirements Management (RM) application is running.
    Affected if The Web UI is accessible and active
  4. Inspect user input fields for sanitization
    Log into DNG/RRC as a standard user, navigate to a requirements artifact, and attempt to create or edit an artifact with a test payload containing HTML/JavaScript characters (such as <script>alert(1)</script> or <img src=x onerror=alert(1)>). Save the artifact and view it to see if the code executes or is rendered as plain text.
    Affected if Arbitrary HTML or JavaScript code renders and executes in the browser instead of being neutralized or displayed as plain text

If IBM DOORS Next Generation or Rational Requirements Composer versions 4.0 through 6.0 are installed with the Web UI enabled, and user-supplied input is not properly sanitized allowing script execution, the environment is affected by CVE-2017-1169.

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 patch for this vulnerability (contact IBM support for specific fix). Additionally, implement input validation and output encoding on all user-supplied data, and configure Content Security Policy (CSP) headers to mitigate XSS execution.

Fix this in Rational Collaborative Lifecycle Management 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-1169 — 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-1169 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