Vulnerabilities > Use of a Broken or Risky Cryptographic Algorithm
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2021-06-16 | CVE-2021-20566 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in IBM Resilient Security Orchestration Automation and Response 38.0 IBM Resilient SOAR V38.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. | 7.5 |
| 2021-06-08 | CVE-2021-22212 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in multiple products ntpkeygen can generate keys that ntpd fails to parse. | 7.4 |
| 2021-05-24 | CVE-2021-20419 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in IBM Security Guardium 11.2 IBM Security Guardium 11.2 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. | 7.5 |
| 2021-05-20 | CVE-2021-27457 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Emerson products A vulnerability has been found in multiple revisions of Emerson Rosemount X-STREAM Gas Analyzer. | 7.5 |
| 2021-05-11 | CVE-2020-24587 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in multiple products The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that all fragments of a frame are encrypted under the same key. | 2.6 |
| 2021-05-11 | CVE-2020-24588 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in multiple products The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that the A-MSDU flag in the plaintext QoS header field is authenticated. | 3.5 |
| 2021-05-11 | CVE-2020-26140 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in multiple products An issue was discovered in the ALFA Windows 10 driver 6.1316.1209 for AWUS036H. | 6.5 |
| 2021-04-26 | CVE-2021-29694 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in IBM Spectrum Protect Plus IBM Spectrum Protect Plus 10.1.0 through 10.1.7 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. | 7.5 |
| 2021-04-12 | CVE-2020-4965 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in IBM products IBM Jazz Team Server products use weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. | 7.5 |
| 2021-04-07 | CVE-2020-36315 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Relic Project Relic In RELIC before 2020-08-01, RSA PKCS#1 v1.5 signature forgery can occur because certain checks of the padding (and of the first two bytes) are inadequate. | 5.3 |