Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
CWE-338
The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.
When a non-cryptographic PRNG is used in a cryptographic context, it can expose the cryptography to certain types of attacks. Often a pseudo-random number generator (PRNG) is not designed for cryptography. Sometimes a mediocre source of randomness is sufficient or preferable for algorithms that use random numbers. Weak generators generally take less processing power and/or do not use the precious, finite, entropy sources on a system. While such PRNGs might have very useful features, these same features could be used to break the cryptography.
We track 99 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.6.
How this weakness is prevented
- Implementation: Use functions or hardware which use a hardware-based random number generation for all crypto. This is the recommended solution. Use CyptGenRandom on Windows, or hw_rand() on Linux.
Latest Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerabilities
- 7.5 High severity
edk2: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
EDK2's Network Package is susceptible to a predictable TCP Initial Sequence Number. This vulnerability can be exploited by an attacker to gain unauthorized access and potentially lead to a loss of Confidentiality.
- 7.5 High severity
edk2: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
EDK2's Network Package is susceptible to a predictable TCP Initial Sequence Number. This vulnerability can be exploited by an attacker to gain unauthorized access and potentially lead to a loss of Confidentiality.
- 9.1 Critical severity
fides: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Fides is an open-source privacy engineering platform for managing the fulfillment of data privacy requests in a runtime environment, and the enforcement of privacy regulations in code. The Fides Privacy Center allows data subject users to submit privacy and co
- 8.8 High severity
Mobile Radio: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
The Motorola MTM5000 series firmwares generate TETRA authentication challenges using a PRNG using a tick count register as its sole entropy source. Low boottime entropy and limited re-seeding of the pool renders the authentication challenge vulnerable to two a
- 7.5 High severity
Libbitcoin Explorer: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
The cryptocurrency wallet entropy seeding mechanism used in Libbitcoin Explorer 3.0.0 through 3.6.0 is weak, aka the Milk Sad issue. The use of an mt19937 Mersenne Twister PRNG restricts the internal entropy to 32 bits regardless of settings. This allows remot
- 9.8 Critical severity
Travianz: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
The cryptographically insecure random number generator being used in TravianZ 8.3.4 and 8.3.3 in the password reset function allows an attacker to guess the password reset.parameters and to take over accounts.
- 9.8 Critical severity
Chatbot: Use of Insufficiently Random Values
Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG), Use of Insufficiently Random Values vulnerability in CBOT Chatbot allows Signature Spoofing by Key Recreation. This issue affects Chatbot: before Core: v4.0.3.4 Panel: v4.0.3.7.
- 7.5 High severity
security-advisories: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Nextcloud server is an open source home cloud implementation. In affected versions the generated fallback password when creating a share was using a weak complexity random number generator, so when the sharer did not change it the password could be guessable t
- 7.5 High severity
Osprey Pump Controller: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Osprey Pump Controller version 1.01 is vulnerable to a weak session token generation algorithm that can be predicted and can aid in authentication and authorization bypass. This may allow an attacker to hijack a session by predicting the session id and gain un
- 8.8 High severity
onedev: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Onedev is a self-hosted Git Server with CI/CD and Kanban. In versions prior to 7.9.12 the algorithm used to generate access token and password reset keys was not cryptographically secure. Existing normal users (or everyone if it allows self-registration) may e
- 8.8 High severity
Dotcms: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
An issue was discovered in dotCMS core 5.3.8.5 through 5.3.8.15 and 21.03 through 22.10.1. A cryptographically insecure random generation algorithm for password-reset token generation leads to account takeover.
- 7.5 High severity
Passeo: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Passeo is an open source python password generator. Versions prior to 1.0.5 rely on the python `random` library for random value selection. The python `random` library warns that it should not be used for security purposes due to its reliance on a non-cryptogr
- 9.1 Critical severity
Node: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
A weak randomness in WebCrypto keygen vulnerability exists in Node.js 18 due to a change with EntropySource() in SecretKeyGenTraits::DoKeyGen() in src/crypto/crypto_keygen.cc. There are two problems with this: 1) It does not check the return value, it assumes
- 9.8 Critical severity
Ootbi: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
An issue was discovered in Object First Ootbi BETA build 1.0.7.712. The authorization service has a flow that allows getting access to the Web UI without knowing credentials. For signing, the JWT token uses a secret key that is generated through a function tha
- 7.5 High severity
Profanity: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
profanity through 1.60 has only four billion possible RNG initializations. Thus, attackers can recover private keys from Ethereum vanity addresses and steal cryptocurrency, as exploited in the wild in June 2022.
- 9.8 Critical severity
NodeBB: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
NodeBB Forum Software is powered by Node.js and supports either Redis, MongoDB, or a PostgreSQL database. It utilizes web sockets for instant interactions and real-time notifications. `utils.generateUUID`, a helper function available in essentially all version
- 7.4 High severity
Cisco IP Phones with Multiplatform Firmware: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
A vulnerability in Cisco Unified IP Phones could allow an unauthenticated, remote attacker to impersonate another user's phone if the Cisco Unified Communications Manager (CUCM) is in secure mode. This vulnerability is due to improper key generation during the
- 7.5 High severity
Download Manager: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
The Download Manager WordPress plugin before 3.2.34 uses the uniqid php function to generate the master key for a download, allowing an attacker to brute force the key with reasonable resources giving direct download access regardless of role based restriction
- 7.5 High severity
Apache CloudStack: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Apache CloudStack prior to 4.16.1.0 used insecure random number generation for project invitation tokens. If a project invite is created based only on an email address, a random token is generated. An attacker with knowledge of the project ID and the fact that