95 matches found
CVE-2026-81822 AVEVA Pipeline Integrity Monitor Use of a Broken or Risky Cryptographic Algorithm
The vulnerability, if exploited, could allow a miscreant with read access to PIMBoards project files to reverse engineer PIMBoards usersā app-native passwords through computational brute-forcing of weak hashes, potentially allowing elevation to a PIMBoards administrator user...
CVE-2020-7001
In Moxa EDS-G516E Series firmware, Version 5.2 or lower, the affected products use a weak cryptographic algorithm, which may allow confidential information to be disclosed...
Exploit for CVE-2025-14175
š CVE-2025-14175 Weak Algorithm Support in SSH Server ā T...
EUVD-2020-28141
Malware in sbrugna...
EUVD-2024-28088
Malicious code in bioql PyPI...
EUVD-2024-16991
Malicious code in bioql PyPI...
Security Bulletin: IBM Sterling Secure Proxy is vulnerable to CVE-2024-38341.
Summary IBM Sterling Secure Proxy is vulnerable due to the use of a weak crypographic algorithm during hashing. Vulnerability Details CVEID:CVE-2024-38341 DESCRIPTION: IBM Sterling Secure Proxy uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly...
CVE-2022-45858
A use of a weak cryptographic algorithm vulnerability CWE-327 in FortiNAC 9.4.1 and below, 9.2.6 and below, 9.1.0 all versions, 8.8.0 all versions, 8.7.0 all versions may increase the chances of an attacker to have access to sensitive information or to perform man-in-the-middle attacks...
Security Bulletin: IBM Security Verify Information Queue uses a relatively weak cryptographic algorithm to protect application data (CVE-2021-20406)
Summary The cryptographic algorithm that IBM Security Verify Information Queue ISIQ uses to encrypt and decrypt application data has a JSON web token JWT signing key that is shorter than the recommended length. As of v10.0.0, ISIQ has doubled the length of its JWT signing key to be in compliance...
CVE-2024-30152
HCL SX v21 is affected by usage of a weak cryptographic algorithm. An attacker could exploit this weakness to gain access to sensitive information, modify data, or other impacts...
CVE-2024-30152
HCL SX v21 is affected by usage of a weak cryptographic algorithm. An attacker could exploit this weakness to gain access to sensitive information, modify data, or other impacts...
CVE-2024-30152 HCL SX is affected by usage of a weak cryptographic algorithm
HCL SX v21 is affected by usage of a weak cryptographic algorithm. An attacker could exploit this weakness to gain access to sensitive information, modify data, or other impacts...
CVE-2024-30152
CVE-2024-30152 concerns HCL SX v21, where the vulnerability arises from the use of a weak cryptographic algorithm. The exposed component is the HCL SX v21 cryptographic handling, leading to potential disclosure of sensitive information and data integrity/availability impacts. Public references in...
CVE-2024-30152 HCL SX is affected by usage of a weak cryptographic algorithm
HCL SX v21 is affected by usage of a weak cryptographic algorithm. An attacker could exploit this weakness to gain access to sensitive information, modify data, or other impacts...
CVE-2025-2539: Use of a Broken or Risky Cryptographic Algorithm
The File Away plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the ajax function in all versions up to, and including, 3.9.9.0.1. This makes it possible for unauthenticated attackers, leveraging the use of a reversible weak algorithm, to read...
PT-2024-32897 Ā· Unknown Ā· Smadar Sps
Name of the Vulnerable Software and Affected Versions: Smadar SPS affected versions not specified Description: The issue is related to the use of a broken or risky cryptographic algorithm, as identified by CWE-327. This could potentially lead to security risks due to the weakness in the...
CVE-2022-43934: Use of a Broken or Risky Cryptographic Algorithm
Brocade SANnav before Brocade SANnav 2.2.2 supports key exchange algorithms, which are considered weak on ports 24, 6514, 18023, 19094, and 19095...
Password Reset Attack
yeswiki/yeswiki is vulnerable to weak cryptographic algorithm. The vulnerability is due to poor cryptographic practices, specifically the use of a weak cryptographic algorithm and a hard-coded salt for hashing the password reset key, allowing attackers to recover the reset key and gain unauthoriz...
GHSA-4FVX-H823-38V3 YesWiki Uses a Broken or Risky Cryptographic Algorithm
Summary The use of a weak cryptographic algorithm and a hard-coded salt to hash the password reset key allows it to be recovered and used to reset the password of any account. Details Firstly, the salt used to hash the password reset key is hard-coded in the includes/services/UserManager.php file...
YesWiki Uses a Broken or Risky Cryptographic Algorithm
Summary The use of a weak cryptographic algorithm and a hard-coded salt to hash the password reset key allows it to be recovered and used to reset the password of any account. Details Firstly, the salt used to hash the password reset key is hard-coded in the includes/services/UserManager.php file...