dbcve.org
Collaborative Lifecycle ManagementApplication · Ibm

CVE-2020-4495

HIGH · 8.8 CVSS v3.1 Published 2021-06-02
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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 could allow a remote attacker to bypass security restrictions, caused by improper access control. By sending a specially-crafted request to the REST API, an attacker could exploit this vulnerability to bypass access restrictions, and execute arbitrary actions with administrative privileges. IBM X-Force ID: 182114.

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

A detailed technical summary for this CVE is being prepared.

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.6= 6.0.6.1
Engineering Lifecycle ManagementApplication
Affected:= 7.0= 7.0.1= 7.0.2
Engineering Lifecycle Optimization Engineering InsightsApplication
Affected:= 7.0= 7.0.1= 7.0.2
Engineering Lifecycle Optimization PublishingApplication
Affected:= 7.0= 7.0.1= 7.0.2
Engineering Test ManagementApplication
Affected:= 7.0.0= 7.0.1
Rational Doors Next GenerationApplication
Affected:= 6.0.6= 6.0.6.1= 7.0= 7.0.1= 7.0.2
Rational Engineering Lifecycle ManagerApplication
Affected:= 6.0.6= 6.0.6.1
Rational Quality 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.ibm.com →
Recommended fix High confidence

Apply the IBM interim fix (iFix) for your specific product version from the vendor support page. For 6.0.x versions, upgrade to a patched 6.0.6.x release. For 7.0.x versions, apply the 7.0.2.x or later iFix.

  1. 1. Navigate to the IBM Support page for this vulnerability: https://www.ibm.com/support/pages/node/6457739
  2. 2. Identify your specific IBM product and current version from the affected versions list
  3. 3. Download the appropriate interim fix (iFix) or patch for your product version from the IBM support page
  4. 4. Back up your existing IBM Jazz/Engineering product installation and database before applying any patch
  5. 5. Apply the patch following the instructions provided in the IBM fix documentation
  6. 6. Restart the affected IBM Jazz server and all dependent services
  7. 7. Verify the patch was applied successfully by checking the installed version or fix pack level
  8. 8. Test that the REST API access controls are functioning properly after the patch
Caveat Review IBM release notes for any configuration or compatibility changes that may affect your existing integrations or customizations

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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