Vulnerabilities > Use of a Broken or Risky Cryptographic Algorithm
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2020-01-09 | CVE-2020-1826 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Huawei Honor Magic2 Firmware Huawei Honor Magic2 mobile phones with versions earlier than 10.0.0.175(C00E59R2P11) have an information leak vulnerability. | 4.4 |
| 2019-12-18 | CVE-2019-4609 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in IBM API Connect 2018.4.1.7 IBM API Connect 2018.4.1.7 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. | 7.5 |
| 2019-12-17 | CVE-2019-18832 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Barco Clickshare Button R9861500D01 Firmware Barco ClickShare Button R9861500D01 devices before 1.9.0 have incorrect Credentials Management. | 8.1 |
| 2019-12-12 | CVE-2019-18340 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Siemens products A vulnerability has been identified in Control Center Server (CCS) (All versions < V1.5.0), Control Center Server (CCS) (All versions >= V1.5.0), SiNVR/SiVMS Video Server (All versions < V5.0.0), SiNVR/SiVMS Video Server (All versions >= V5.0.0). | 5.5 |
| 2019-12-12 | CVE-2019-17428 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Intesync Solismed 3.3 An issue was discovered in Intesync Solismed 3.3sp1. | 5.9 |
| 2019-11-08 | CVE-2019-16208 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Broadcom Brocade Sannav 1.1.0/1.1.1 Password-based encryption (PBE) algorithm, of Brocade SANnav versions before v2.0, has a weakness in generating cryptographic keys that may allow an attacker to decrypt passwords used with several services (Radius, TACAS, etc.). | 7.5 |
| 2019-10-25 | CVE-2019-4399 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in IBM Cloud Orchestrator IBM Cloud Orchestrator 2.4 through 2.4.0.5 and 2.5 through 2.5.0.9 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. | 7.5 |
| 2019-10-23 | CVE-2019-8237 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Adobe Acrobat DC Adobe Acrobat and Reader versions 2019.012.20035 and earlier, 2019.012.20035 and earlier, 2017.011.30142 and earlier, 2017.011.30143 and earlier, 2015.006.30497 and earlier, and 2015.006.30498 and earlier have an insufficiently robust encryption vulnerability. | 9.8 |
| 2019-10-09 | CVE-2019-11341 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Google Android 9.0 On certain Samsung P(9.0) phones, an attacker with physical access can start a TCP Dump capture without the user's knowledge. | 4.6 |
| 2019-10-09 | CVE-2018-5745 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in ISC Bind "managed-keys" is a feature which allows a BIND resolver to automatically maintain the keys used by trust anchors which operators configure for use in DNSSEC validation. | 4.9 |