dbcve.org
Rational Doors Next GenerationApplication · Ibm

CVE-2017-1546

MEDIUM · 5.4 CVSS v3.0 Published 2017-12-13
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) 4.07, 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: 130915.

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 versions 4.07, 5.0, and 6.0 contains a cross-site scripting vulnerability in its web interface. Attackers can inject arbitrary JavaScript code through the UI, which executes in the context of other users' trusted sessions, potentially leading to credential disclosure or session hijacking.

MitigationApply vendor-supplied patches for this vulnerability. Implement output encoding and input validation across all user-supplied data fields in the web interface. Consider deploying Content Security Policy 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 Doors Next GenerationApplication
Affected:= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4
Rational Requirements ComposerApplication
Affected:= 4.0= 4.0.7= 5.0= 5.0.1= 5.0.2

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 DOORS Next Generation version
    Check the installed IBM Rational DOORS Next Generation version by accessing the About section in the web interface (typically at /rm/about) or by checking the installation directory for version files. In a deployment using WebSphere, check the installed applications via the WebSphere Administration Console.
    Affected if The installed version equals 6.0, 6.0.1, 6.0.2, 6.0.3, or 6.0.4
  2. Identify installed Rational Requirements Composer version
    Check the installed IBM Rational Requirements Composer version by accessing the About section in the web interface or checking the installation directory and configuration files for version information.
    Affected if The installed version equals 4.0, 4.0.7, 5.0, 5.0.1, or 5.0.2
  3. Confirm web interface is enabled and exposed
    Verify that the IBM Rational DOORS Next Generation or Rational Requirements Composer web interface is enabled and accessible. Check the application server (WebSphere or Tomcat) configuration to confirm the RM/NG web application is running and exposed on a network-accessible URL.
    Affected if The web interface is enabled and accessible to users or attackers on the network
  4. Check for Content Security Policy headers
    Inspect HTTP responses from the web interface using browser developer tools or a command-line tool (curl -I <url>) to see if Content-Security-Policy headers are present. Also check the web server or application server configuration for CSP header definitions.
    Affected if No Content-Security-Policy header is present and the web interface is accessible

You are affected if your environment runs IBM Rational DOORS Next Generation versions 6.0-6.0.4 or Rational Requirements Composer versions 4.0, 4.0.7, or 5.0-5.0.2, with the web interface enabled and accessible.

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 vendor-supplied patches for this vulnerability. Implement output encoding and input validation across all user-supplied data fields in the web interface. Consider deploying Content Security Policy headers to mitigate XSS execution.

Fix this in Rational Doors Next Generation Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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