CVE-2020-4965

CVE-2020-4965 is a high-severity vulnerability in Ibm Collaborative Lifecycle Management with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-327.

Key facts

Description

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.

Frequently asked questions

What is CVE-2020-4965?
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.
How severe is CVE-2020-4965?
CVE-2020-4965 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2020-4965 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (49th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-4965?
CVE-2020-4965 primarily affects Ibm Collaborative Lifecycle Management. In total, 38 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2020-4965?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-4965 published?
CVE-2020-4965 was published on 2021-04-12 and last updated on 2026-06-17.

References

Affected products (38)

More vulnerabilities in Ibm Collaborative Lifecycle Management

All CVEs affecting Ibm Collaborative Lifecycle Management →

Other CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities

Browse all CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities →