CVE-2020-4965 json
IBM Jazz Team Server products use weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive in…
published 5y ago modified 4mo ago also EUVD-2020-26212
- cvss
- 5.9
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
IBM Jazz Team Server products use weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 192422.
Patch / fix
- ibm.com/support/pages/node/6441803 advisory
Is CVE-2020-4965 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 5.9 | CVSS:3.0/C:H/I:N/A:N/UI:N/S:U/AC:H/AV:N/PR:N/RL:O/E:U/RC:C |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.0 | 5.9 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- IBM Rational DOORS Next Generation
- IBM Engineering Test Management
- IBM Rational Collaborative Lifecycle Management
- IBM Rational Engineering Lifecycle Manager
- IBM Rational Quality Manager
- IBM Rational Team Concert
- IBM Rational Rhapsody Model Manager
- IBM Engineering Workflow Management
- IBM Engineering Lifecycle Optimization
Classification
- Weakness
-
- CWE-327 Use of a Broken or Risky Cryptographic Algorithm
References
-
ibm.com
/support/pages/node/6441803
patch, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/192422
vdb-entry
Sources
- CVE List CVE-2020-4965
- NVD CVE-2020-4965
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.