dbcve.org
Doors NextApplication · Ibm

CVE-2020-4445

MEDIUM · 5.4 CVSS v3.1 Published 2020-09-02
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 Jazz Team Server based Applications 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: 181122.

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 Jazz Team Server based Applications are vulnerable to stored cross-site scripting (XSS). Attackers can embed arbitrary JavaScript code into the Web UI through unsanitized input fields, potentially altering application functionality and allowing credential theft within trusted sessions.

MitigationImplement robust input validation and output encoding for all user-supplied data rendered in the Web UI. Apply context-specific sanitization and deploy 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
Doors NextApplication
Affected:= 7.0
Engineering Requirements Management Doors NextApplication
Affected:= 7.0.1
Engineering Test ManagementApplication
Affected:= 7.0.0
Engineering Workflow ManagementApplication
Affected:= 7.0.0= 7.0.1
EniApplication
Affected:= 7.0
Rational Collaborative Lifecycle ManagementApplication
Affected:= 6.0.2= 6.0.6= 6.0.6.1
Rational Doors Next GenerationApplication
Affected:= 6.0.2= 6.0.6= 6.0.6.1
Rational Engineering Lifecycle ManagerApplication
Affected:= 6.0.2= 6.0.6= 6.0.6.1= 7.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.1/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 Jazz-based product
    Check the application server or installed software for the product name (IBM Doors Next, Rational CLM, Engineering Test Management, etc.) and confirm it is one of the affected products listed in the CVE
    Affected if The installed product matches any of: Doors Next, Engineering Requirements Management Doors Next, Engineering Test Management, Engineering Workflow Management, Eni, Rational Collaborative Lifecycle Management, Rational Doors Next Generation, or Rational Engineering Lifecycle Manager
  2. Determine the installed product version
    Use the product's About or version information panel, or check the installation directory for a version file. Common paths include the IBM Jazz team server administration console or the application's help/about section
    Affected if The installed version exactly matches: 7.0, 7.0.1, 7.0.0, 6.0.2, 6.0.6, 6.0.6.1, or 7.0 as listed in the affected products and versions
  3. Verify Web UI accessibility
    Confirm the web-based user interface is enabled and accessible by accessing the application's URL (typically on port 9443 or similar for IBM Jazz applications)
    Affected if The Web UI is accessible and users can log in to submit or modify data through input fields
  4. Review application logs for XSS indicators
    Examine IBM Jazz application logs (typically found in <install_dir>/logs or through the Jazz Team Server administrative console) for unusual script tags or JavaScript patterns in user input fields
    Affected if Logs contain unsanitized script tags or JavaScript code submitted through user input fields that were not properly encoded when displayed

A defender is affected if they are running any of the listed IBM Jazz-based products at the specific versions (7.0, 7.0.1, 7.0.0, 6.0.2, 6.0.6, or 6.0.6.1) and the Web UI is accessible to users who can input data.

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

Implement robust input validation and output encoding for all user-supplied data rendered in the Web UI. Apply context-specific sanitization and deploy Content Security Policy (CSP) headers to mitigate XSS execution.

Fix this in Doors Next 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-2020-4445 — 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-2020-4445 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