CVE-2020-4624
First published: Thu Nov 05 2020(Updated: )
IBM Cloud Pak for Security (CP4S) uses weaker than expected cryptographic algorithms during negotiation could allow an attacker to decrypt sensitive information.
Credit: psirt@us.ibm.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| =1.3.0.1 | ||
| IBM Cloud Pak for Security | <=1.3.0.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-4624?
CVE-2020-4624 has a medium severity rating due to the potential for sensitive information to be decrypted.
How do I fix CVE-2020-4624?
To fix CVE-2020-4624, upgrade IBM Cloud Pak for Security to a version that uses stronger cryptographic algorithms.
What are the potential impacts of CVE-2020-4624?
The impacts of CVE-2020-4624 include unauthorized decryption of sensitive data, which could lead to data breaches.
Which software versions are affected by CVE-2020-4624?
CVE-2020-4624 affects IBM Cloud Pak for Security version 1.3.0.1.
Is there a workaround for CVE-2020-4624?
There are currently no recommended workarounds for mitigating CVE-2020-4624; upgrading is the preferred solution.
- collector/nvd-index
- agent/references
- agent/type
- agent/first-publish-date
- agent/severity
- agent/remedy
- agent/weakness
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/ibm-support
- source/IBM
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/ibm
- canonical/ibm cloud pak for security
- version/ibm cloud pak for security/1.3.0.1