Vulnerabilities > Use of a Broken or Risky Cryptographic Algorithm
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2023-10-06 | CVE-2022-33160 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in IBM Security Directory Suite VA 8.0.1 IBM Security Directory Suite 8.0.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. | 7.5 |
| 2023-09-21 | CVE-2023-39252 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Dell Secure Connect Gateway Policy Manager 5.16.00.14 Dell SCG Policy Manager 5.16.00.14 contains a broken cryptographic algorithm vulnerability. | 5.9 |
| 2023-09-20 | CVE-2023-43635 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Linuxfoundation Edge Virtualization Engine Vault Key Sealed With SHA1 PCRs The measured boot solution implemented in EVE OS leans on a PCR locking mechanism. Different parts of the system update different PCR values in the TPM, resulting in a unique value for each PCR entry. These PCRs are then used in order to seal/unseal a key from the TPM which is used to encrypt/decrypt the “vault” directory. This “vault” directory is the most sensitive point in the system and as such, its content should be protected. This mechanism is noted in Zededa’s documentation as the “measured boot” mechanism, designed to protect said “vault”. The code that’s responsible for generating and fetching the key from the TPM assumes that SHA256 PCRs are used in order to seal/unseal the key, and as such their presence is being checked. The issue here is that the key is not sealed using SHA256 PCRs, but using SHA1 PCRs. This leads to several issues: • Machines that have their SHA256 PCRs enabled but SHA1 PCRs disabled, as well as not sealing their keys at all, meaning the “vault” is not protected from an attacker. • SHA1 is considered insecure and reduces the complexity level required to unseal the key in machines which have their SHA1 PCRs enabled. An attacker can very easily retrieve the contents of the “vault”, which will effectively render the “measured boot” mechanism meaningless. | 8.8 |
| 2023-08-29 | CVE-2023-34039 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in VMWare Aria Operations for Networks Aria Operations for Networks contains an Authentication Bypass vulnerability due to a lack of unique cryptographic key generation. A malicious actor with network access to Aria Operations for Networks could bypass SSH authentication to gain access to the Aria Operations for Networks CLI. | 9.8 |
| 2023-08-28 | CVE-2023-34758 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Bishopfox Sliver Sliver from v1.5.x to v1.5.39 has an improper cryptographic implementation, which allows attackers to execute a man-in-the-middle attack via intercepted and crafted responses. | 8.1 |
| 2023-08-27 | CVE-2023-38730 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in IBM Storage Copy Data Management IBM Storage Copy Data Management 2.2.0.0 through 2.2.19.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. | 7.5 |
| 2023-08-24 | CVE-2023-40371 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in IBM AIX and Vios IBM AIX 7.2, 7.3, VIOS 3.1's OpenSSH implementation could allow a non-privileged local user to access files outside of those allowed due to improper access controls. | 5.5 |
| 2023-08-15 | CVE-2023-4326 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Broadcom Raid Controller web Interface 51.12.02779 Broadcom RAID Controller web interface is vulnerable has an insecure default TLS configuration that supports obsolete SHA1-based ciphersuites | 7.5 |
| 2023-08-15 | CVE-2023-4331 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Broadcom Raid Controller web Interface 51.12.02779 Broadcom RAID Controller web interface is vulnerable has an insecure default TLS configuration that support obsolete and vulnerable TLS protocols | 7.5 |
| 2023-08-09 | CVE-2023-23347 | Use of a Broken or Risky Cryptographic Algorithm vulnerability in Hcltech Dryice Iautomate 6.0/6.1/6.2 HCL DRYiCE iAutomate is affected by the use of a broken cryptographic algorithm. | 7.1 |