Vulnerabilities > Use of a Broken or Risky Cryptographic Algorithm
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2022-03-04 | CVE-2021-27756 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Hcltech Bigfix Compliance 2.0/2.0.5 "TLS-RSA cipher suites are not disabled in BigFix Compliance up to v2.0.5. | 7.5 |
| 2022-03-03 | CVE-2021-43774 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Fujifilm products A risky-algorithm issue was discovered on Fujifilm DocuCentre-VI C4471 1.8 devices. | 4.9 |
| 2022-02-28 | CVE-2022-0377 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Thimpress Learnpress Users of the LearnPress WordPress plugin before 4.1.5 can upload an image as a profile avatar after the registration. | 4.3 |
| 2022-02-26 | CVE-2020-36516 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in multiple products An issue was discovered in the Linux kernel through 5.16.11. | 5.9 |
| 2022-01-21 | CVE-2021-31562 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Fresenius-Kabi products The SSL/TLS configuration of Fresenius Kabi Agilia Link + version 3.0 has serious deficiencies that may allow an attacker to compromise SSL/TLS sessions in different ways. | 9.1 |
| 2022-01-21 | CVE-2021-33846 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Fresenius-Kabi products Fresenius Kabi Vigilant Software Suite (Mastermed Dashboard) version 2.0.1.3 issues authentication tokens to authenticated users that are signed with a symmetric encryption key. | 7.2 |
| 2022-01-10 | CVE-2021-38921 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in IBM Security Verify Access 10.0.0/10.0.1.0/10.0.2.0 IBM Security Verify 10.0.0, 10.0.1.0, and 10.0.2.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. | 7.5 |
| 2022-01-10 | CVE-2021-40006 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Huawei Harmonyos 2.0 Vulnerability of design defects in the security algorithm component. | 4.6 |
| 2022-01-04 | CVE-2021-38542 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Apache James 2.2.0/3.3.0/3.4.0 Apache James prior to release 3.6.1 is vulnerable to a buffering attack relying on the use of the STARTTLS command. | 5.9 |
| 2021-12-28 | CVE-2021-42583 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Foxcpp Maddy A Broken or Risky Cryptographic Algorithm exists in Max Mazurov Maddy before 0.5.2, which is an unnecessary risk that may result in the exposure of sensitive information. | 7.5 |