402 matches found
CVE-2021-42216
The CVE-2021-42216 entry concerns AnonAddy 0.8.5 with a broken or risky cryptographic algorithm in VerificationController.php. Affected software: AnonAddy (version 0.8.5). Vulnerable component: VerificationController.php; root cause: use of a broken or risky cryptographic algorithm. Impact (per C...
CVE-2021-42216: Inadequate Encryption Strength
A Broken or Risky Cryptographic Algorithm exists in AnonAddy 0.8.5 via VerificationController.php...
CVE-2021-39002: Use of a Broken or Risky Cryptographic Algorithm
IBM DB2 for Linux, UNIX and Windows includes DB2 Connect Server 9.7, 10.1, 10.5, 11.1, and 11.5 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information...
CVE-2021-39182 Use of Password Hash With Insufficient Computational Effort and Use of a Broken or Risky Cryptographic Algorithm and Reversible One-Way Hash in hashing.py
EnroCrypt is a Python module for encryption and hashing. Prior to version 1.1.4, EnroCrypt used the MD5 hashing algorithm in the hashing file. Beginners who are unfamiliar with hashes can face problems as MD5 is considered an insecure hashing algorithm. The vulnerability is patched in v1.1.4 of t...
CVE-2021-39182: Use of a Broken or Risky Cryptographic Algorithm
EnroCrypt is a Python module for encryption and hashing. Prior to version 1.1.4, EnroCrypt used the MD5 hashing algorithm in the hashing file. Beginners who are unfamiliar with hashes can face problems as MD5 is considered an insecure hashing algorithm. The vulnerability is patched in v1.1.4 of t...
CVE-2021-36298: Use of a Broken or Risky Cryptographic Algorithm
Dell EMC InsightIQ, versions prior to 4.1.4, contain risky cryptographic algorithms in the SSH component. A remote unauthenticated attacker could potentially exploit this vulnerability leading to authentication bypass and remote takeover of the InsightIQ. This allows an attacker to take complete...
CVE-2021-31796: Use of a Broken or Risky Cryptographic Algorithm
An inadequate encryption vulnerability discovered in CyberArk Credential Provider before 12.1 may lead to Information Disclosure. An attacker may realistically have enough information that the number of possible keys for a credential file is only one, and the number is usually not higher than 2^3...
Use of a Broken or Risky Cryptographic Algorithm
✍️ Description The function mtrand is used to generate session tokens, this function is cryptographically flawed due to its nature being one pseudorandomness, an attacker can take advantage of the cryptographically insecure nature of this function to enumerate session tokens for accounts that are...
CVE-2021-29722: Use of a Broken or Risky Cryptographic Algorithm
IBM Sterling Secure Proxy 6.0.1, 6.0.2, 2.4.3.2, and 3.4.3.2 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 201095...
CVE-2021-37588: Use of a Broken or Risky Cryptographic Algorithm
In Charm 0.43, any two users can collude to achieve the ability to decrypt YCT14 data...
CVE-2021-37587: Use of a Broken or Risky Cryptographic Algorithm
In Charm 0.43, any single user can decrypt DAC-MACS or MA-ABE-YJ14 data...
CVE-2021-2351: Use of a Broken or Risky Cryptographic Algorithm
Vulnerability in the Advanced Networking Option component of Oracle Database Server. Supported versions that are affected are 12.1.0.2, 12.2.0.1 and 19c. Difficult to exploit vulnerability allows unauthenticated attacker with network access via Oracle Net to compromise Advanced Networking Option...
CVE-2021-29794: Use of a Broken or Risky Cryptographic Algorithm
IBM Tivoli Netcool/Impact 7.1.0.20 and 7.1.0.21 uses an insecure SSH server configuration which enables weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 203556...
CVE-2021-22212: Use of a Broken or Risky Cryptographic Algorithm
ntpkeygen can generate keys that ntpd fails to parse. NTPsec 1.2.0 allows ntpkeygen to generate keys with '' characters. ntpd then either pads, shortens the key, or fails to load these keys entirely, depending on the key type and the placement of the ''. This results in the administrator not bein...
CVE-2021-22738: Use of a Broken or Risky Cryptographic Algorithm
Use of a Broken or Risky Cryptographic Algorithm vulnerability exists in homeLYnk Wiser For KNX and spaceLYnk V2.60 and prior that could cause unauthorized access when credentials are discovered after a brute force attack...
Siemens and PKE Control Center Server
1. EXECUTIVE SUMMARY CVSS v3 9.9 ATTENTION: Exploitable remotely/low attack complexity Vendors: Siemens/PKE Equipment: Control Center Server CCS Vulnerabilities: Cleartext Storage of Sensitive Information in GUI, Improper Authentication, Relative Path Traversal, Use of a Broken or Risky...
CVE-2020-36315: Use of a Broken or Risky Cryptographic Algorithm
In RELIC before 2020-08-01, RSA PKCS1 v1.5 signature forgery can occur because certain checks of the padding and of the first two bytes are inadequate. NOTE: this requires that a low public exponent such as 3 is being used. The product, by default, does not generate RSA keys with such a low numbe...
CVE-2021-3446: Use of a Broken or Risky Cryptographic Algorithm
A flaw was found in libtpms in versions before 0.8.2. The commonly used integration of libtpms with OpenSSL contained a vulnerability related to the returned IV initialization vector when certain symmetric ciphers were used. Instead of returning the last IV it returned the initial IV to the calle...
CVE-2020-14246: Use of a Broken or Risky Cryptographic Algorithm
HCL OneTest Performance V9.5, V10.0, V10.1 uses basic authentication which is relatively weak. An attacker could potentially decode the encoded credentials...
CVE-2020-4968: Use of a Broken or Risky Cryptographic Algorithm
IBM Security Identity Governance and Intelligence 5.2.6 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 192427...