dbcve.org
Collaborative Lifecycle ManagementApplication · Ibm

CVE-2020-4733

MEDIUM · 5.4 CVSS v3.1 Published 2021-01-08
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 Foundation products 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: 188127.

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

Cross-site scripting (XSS) vulnerability in IBM Jazz Foundation products allowing authenticated users to embed arbitrary JavaScript code in the Web UI, potentially altering functionality and leading to credential disclosure within trusted sessions.

MitigationApply IBM's security patch for CVE-2020-4733; implement proper input validation and output encoding for all user-supplied data in the Web UI to prevent JavaScript injection.

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
Collaborative Lifecycle ManagementApplication
Affected:= 6.0.2= 6.0.6= 6.0.6.1
Doors NextApplication
Affected:= 7.0= 7.0.1
Engineering InsightsApplication
Affected:= 7.0= 7.0.1
Engineering Lifecycle ManagementApplication
Affected:= 7.0= 7.0.1
Engineering Test ManagementApplication
Affected:= 7.0.0
Engineering Workflow ManagementApplication
Affected:= 7.0= 7.0.1
Rational Doors Next GenerationApplication
Affected:= 6.0.2= 6.0.6= 6.0.6.1
Rational Engineering Lifecycle ManagerApplication
Affected:= 6.0.6= 6.0.6.1

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 product and version
    Check the product version in the IBM Jazz Administration console or by accessing the /admin URL and reviewing the 'About' section. Common paths: https://<server>/<product>/admin or check the installation directory for version.info files.
    Affected if The product matches one of the affected products (IBM Collaborative Lifecycle Management, Doors Next, Engineering Insights, Engineering Lifecycle Management, Engineering Test Management, Engineering Workflow Management, Rational Doors Next Generation, or Rational Engineering Lifecycle Manager) AND t
  2. Confirm the Web UI is enabled and accessible
    Verify the web interface is reachable by accessing the product URL in a browser. For CLM products, this is typically the root URL of the application server (e.g., https://<server>/rm, https://<server>/qm, https://<server>/dm).
    Affected if The Web UI is exposed and accessible over HTTP/HTTPS.
  3. Verify user authentication is configured
    Check the Jazz Team Server administration settings to confirm that user authentication (JTS) is enabled and users can log in. Navigate to Server Administration > Jazz Team Server > Users and Groups.
    Affected if User authentication is enabled and users can log in to the application.
  4. Review Web UI for unvalidated input fields
    Inspect common entry points in the Web UI where user-supplied data is displayed: requirement attributes, test case fields, workflow comments, or any text input areas that render back to the user without proper encoding.
    Affected if The application renders user input in HTML/JavaScript context without visible output encoding or validation.

Your environment is affected if you run any of the listed IBM Jazz Foundation products at versions 6.0.2, 6.0.6, 6.0.6.1, 7.0, 7.0.1, or 7.0.0, with the Web UI accessible and user authentication enabled.

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 for CVE-2020-4733; implement proper input validation and output encoding for all user-supplied data in the Web UI to prevent JavaScript injection.

Fix this in Collaborative Lifecycle Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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