dbcve.org
Engineering Lifecycle OptimizationApplication · Ibm

CVE-2020-5031

MEDIUM · 5.4 CVSS v3.1 Published 2021-07-19
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 and IBM Engineering 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: 193738.

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

A cross-site scripting (XSS) vulnerability in IBM Jazz Foundation and IBM Engineering products allows authenticated users to embed arbitrary JavaScript code into the Web UI. This can manipulate intended functionality and potentially exfiltrate credentials or session data within a trusted session.

MitigationApply IBM patches for Jazz Foundation and affected Engineering products; implement input validation, output encoding, and Content Security Policy headers to prevent XSS 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
Engineering Lifecycle OptimizationApplication
Affected:= 7.0= 7.0.1= 7.0.2
Engineering Workflow ManagementApplication
Affected:= 7.0.0= 7.0.1= 7.0.2
Rational Collaborative Lifecycle ManagementApplication
Affected:= 6.0.6= 6.0.6.1
Rational Doors Next GenerationApplication
Affected:= 7.0= 7.0.1= 7.0.2
Rational Engineering Lifecycle ManagerApplication
Affected:= 7.0= 7.0.1= 7.0.2
Rational Team ConcertApplication
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 product and version
    Access the IBM Jazz Administration dashboard or check the installation directory for version information. For Rational products, open the About dialog from the Help menu. For Engineering products, check the Jazz Team Server administration page.
    Affected if The installed product matches one of the affected versions: Engineering Lifecycle Optimization 7.0-7.0.2, Engineering Workflow Management 7.0.0-7.0.2, Rational Collaborative Lifecycle Management 6.0.6-6.0.6.1, Rational Doors Next Generation 7.0-7.0.2, Rational Engineering Lifecycle Manager 7.0-7.0.2
  2. Confirm Web UI access is enabled
    Verify that the Jazz-based web interface is accessible by navigating to the server URL (typically https://server:port/jazz or the product-specific web context). Check the server configuration files (such as server.xml or web.xml in the installation directory) for enabled status.
    Affected if The Web UI is exposed and accessible to users.
  3. Verify user authentication is configured
    Check the Jazz Team Server or application server security settings. Review the teamserver.properties file or the administration console to confirm that form-based or basic authentication is enabled and user repositories are configured.
    Affected if User authentication is enabled, allowing authenticated users to access the web interface.
  4. Check for recent security updates
    Review the IBM Fix Central or the installed patches list. Look for IBM Jazz Foundation patches or product-specific security patches released after the CVE disclosure date.
    Affected if No security patches for CVE-2020-5031 have been applied to the Jazz Foundation components.

Your environment is affected if you are running any of the listed product versions with the Web UI enabled and user authentication configured, and no corresponding security patches have been applied.

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 patches for Jazz Foundation and affected Engineering products; implement input validation, output encoding, and Content Security Policy headers to prevent XSS injection.

Fix this in Engineering Lifecycle Optimization 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-2020-5031 — 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-5031 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