dbcve.org
Doors NextApplication · Ibm

CVE-2020-4522

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

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 Jazz Team Server based Applications contain a stored cross-site scripting (XSS) vulnerability allowing authenticated users to embed arbitrary JavaScript code into the Web UI. This can alter application functionality and potentially enable credential disclosure through execution in trusted user sessions.

MitigationApply IBM's security patch when available. Implement input validation and output encoding for user-supplied content. Deploy Content Security Policy (CSP) headers and consider a WAF for additional protection.

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
    Locate the application version through the Jazz Team Server admin console, About section, or by querying the server's diagnostic endpoints typically found at /admin or /jts/about
    Affected if The product matches any of the following: IBM Doors Next 7.0, IBM Engineering Requirements Management Doors Next 7.0.1, IBM Engineering Test Management 7.0.0, IBM Engineering Workflow Management 7.0.0 or 7.0.1, IBM Eni 7.0, IBM Rational Collaborative Lifecycle Management 6.0.2, 6.0.6, or 6.0.6.1, IB
  2. Confirm Web UI is enabled
    Access the application's web interface through a browser or API client using the public URL path such as /rm, /qm, /rm or the CLM welcome page
    Affected if The Web UI is accessible and users can log in through the browser interface
  3. Verify user authentication is configured
    Check that the Jazz Team Server has user authentication enabled and that user accounts exist in the configured user registry (internal or external LDAP)
    Affected if Authenticated user sessions can be established in the application
  4. Identify Web UI input fields vulnerable to stored XSS
    In the Web UI, navigate to fields that accept user-supplied content such as artifact descriptions, comments, tags, or custom attributes. Submit test content with script tags in these fields and verify if the content is rendered without encoding
    Affected if The application stores and displays user-provided content in the Web UI without proper output encoding, allowing embedded script execution

Environment is affected if running any listed IBM Jazz-based product at the specified versions with the Web UI accessible to authenticated users who can embed unsanitized script content into UI fields.

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 security patch when available. Implement input validation and output encoding for user-supplied content. Deploy Content Security Policy (CSP) headers and consider a WAF for additional protection.

Fix this in Doors Next Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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