CVE-2020-5004
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 · uneditedIBM 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: 192957.
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 confidenceIBM Jazz Foundation products contain a stored cross-site scripting (XSS) vulnerability in the Web UI. Attackers can inject arbitrary JavaScript code that executes within the context of trusted user sessions, potentially leading to credential disclosure or session hijacking.
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= 7.0= 7.0.1= 7.0.2all versions= 7.0.0= 7.0.1= 7.0.2= 7.0= 7.0.1= 7.0.2= 6.0.2= 6.0.6= 6.0.6.1= 6.0.6= 6.0.6.1= 7.0= 7.0.1= 7.0.2= 6.0.2= 6.0.6= 6.0.6.1= 6.0.6= 6.0.6.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed IBM Jazz productAccess the Jazz application web interface and navigate to the About section (typically via the user menu or Help > About). Alternatively, check the installation directory for version files or check the admin console for product version information.Affected if The product is one of: Engineering Lifecycle Optimization - Engineering Insights, Engineering Requirements Quality Assistant On Premises, Engineering Test Management, Engineering Workflow Management, Rational Collaborative Lifecycle Management, Rational Doors Next Generation, Rational Engineering Li
-
Confirm the exact version numberLocate the precise version string in the About dialog, installation manifest, or admin interface. Record the full version (e.g., 7.0.1, 6.0.6.1).Affected if A specific version match is required for accurate assessment.
-
Compare installed version against affected rangesMatch your confirmed version to the affected list: Engineering Insights 7.0 through 7.0.2; Engineering Test Management 7.0.0 through 7.0.2; Engineering Workflow Management 7.0 through 7.0.2; Rational CLM 6.0.2, 6.0.6, or 6.0.6.1; Rational Doors Next Generation 6.0.6, 6.0.6.1, or 7.0 through 7.0.2; Rational Engineering Lifecycle Manager 6.0.2, 6.0.6, or 6.0.6.1; Rational Quality Manager 6.0.6 or 6.0.6.1; or any version of Engineering Requirements Quality Assistant On Premises.Affected if The installed version exactly matches any version listed in the affected products and versions.
-
Verify Web UI is accessibleConfirm that the Jazz web interface is enabled and accessible to users. The vulnerability exists in the Web UI component.Affected if The Web UI is enabled and users can interact with it.
-
Check for evidence of XSS exploitationReview server logs and application audit trails for suspicious script injection patterns in user-generated fields, artifacts, or comments. Look for encoded or obfuscated JavaScript payloads in content that could indicate attempted exploitation.Affected if Unusual script tags or JavaScript code are found embedded in user content fields or artifacts.
Your environment is affected if you are running any of the listed IBM Jazz products at the specific versions specified and the Web UI is enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataApply IBM's security patch for CVE-2020-5004. Until patched, implement output encoding and input validation as compensating controls. Review user-generated content handling in the affected Jazz interfaces.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5004 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-5004 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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