Skip to content
OpenAdvisories

Weakness (CWE)

CWE-331: Insufficient Entropy

Base Draft

The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.

How to prevent it (1 mitigation)
  1. Implementation

    Determine the necessary entropy to adequately provide for randomness and predictability. This can be achieved by increasing the number of bits of objects such as keys and seeds.

Source: MITRE CWE-331

40 results · Clear filters · Feed

  • Medium 4.7

    Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to 5.36.00.00, contains…

  • Medium 5.1

    Power System Insufficient Entropy

    IBM PowerVM Hypervisor Platform KeyStore (PKS) and virtual TPM FW1110.00 through FW1110.20, FW1060.00 through FW1060.71, and FW950.00 through FW950.H2 use persistent storage key seeds that result in an AES key with reduced strength. An attacker with access to…

  • Medium 5.3

    Power System Insufficient Entropy

    IBM PowerVM Hypervisor FW1110.00 through FW1110.20, FW1060.00 through FW1060.71, and FW950.00 through FW950.H2 could allow a local attacker with administrative privileges to decrypt encrypted data due to certain hypervisor calls utilizing less entropy than re…

  • Medium 6.9

    Weak Session Key Generation in TP-Link Omada Adoption Protocol

    A cryptographic weakness exists in the Omada adoption protocol where session encryption keys used to protect communications between controllers and managed devices may be predictable due to insufficient entropy in session key generation. An attacker who succe…

  • Medium 4.2

    This Power System update is being released to address Insufficient Entropy

    IBM PowerVM Hypervisor FW1110.00 through FW1110.20, and FW1060.00 through FW1060.71 could allow an attacker with physical access to the Transparent Memory Encryption (TME) hardware to decrypt encrypted memory due to insufficient cryptographic entropy.

  • Medium 5.1

    Insufficient Entropy in Raspberry Pi 5 and Compute Module 5

    EEPROM firmware on Raspberry Pi 5 and Compute Module 5 devices produced non-random KASLR and RNG seed values. This resulted in consistent kernel addresses across boots and devices, potentially making it easier to exploit other vulnerabilities. Additionally, t…

  • Medium 4.1

    Insufficient DPA countermeasure reseeding

    * Countermeasures for DPA within SYMCRYPTO engine on SixG301xxx devices are not sufficiently random and will eventually repeat. * KSU keys using SYMCRYPTO will be impacted by this vulnerability.

  • Medium 6.3

    The expat and elementtree parsers use insufficient entropy for XML hash-flooding protection

    `xml.parsers.expat` and `xml.etree.ElementTree` use insufficient entropy for Expat hash-flooding protection, which allows a crafted XML document to trigger hash flooding.\r\n\r\nFully mitigating this vulnerability requires both updating libexpat to 2.8.0 or l…

  • Medium 5.3

    Insufficient Entropy Vulnerability in Telerik UI for ASP.NET AJAX

    In Progress® Telerik® UI for AJAX, versions prior to 2026.1.225, an insufficient entropy vulnerability exists in RadAsyncUpload, where a predictable temporary identifier, based on timestamp and filename, can enable collisions and file content tampering.

  • Medium 4.8

    Glibc: vdso getrandom acceleration may return predictable randomness

    An insufficient entropy vulnerability was found in glibc. The getrandom and arc4random family of functions may return predictable randomness if these functions are called again after the fork, which happens concurrently with a call to any of these functions.

  • Medium 6.4

    Micca KE700 Brute-force vulnerability due to low entropy

    The Micca KE700 system relies on a 6-bit portion of an identifier for authentication within rolling codes, providing only 64 possible combinations. This low entropy allows an attacker to perform a brute-force attack against one component of the rolling code. …

  • Medium 6.8
    CVE-2026-1814 Public exploit

    Rapid7 Nexpose Insecure Java Keystore Password Generation

    Rapid7 Nexpose versions 6.4.50 and later are vulnerable to an insufficient entropy issue in the CredentialsKeyStorePassword.generateRandomPassword() method. When updating legacy keystore passwords, the application generates a new password with insufficient le…

  • Medium 4.7

    The KDE Connect verification-code protocol before 2025-04-18 uses only 8 characters and therefore allows brute-force at…

  • Medium 6.3

    Insufficient Entropy in Password Generation

    A deterministic three‑character prefix in the Password Generation component of TYPO3 CMS versions 12.0.0–12.4.36 and 13.0.0–13.4.17 reduces entropy, allowing attackers to carry out brute‑force attacks more quickly.

  • Medium 6.9

    Thinbus generates insufficient entropy: 252 bits vs minimum 256 bits

    Thinbus Javascript Secure Remote Password is a browser SRP6a implementation for zero-knowledge password authentication. In versions 2.0.0 and below, a protocol compliance bug causes the client to generate a fixed 252 bits of entropy instead of the intended bi…

  • Medium 4.0

    Crypt::CBC versions between 1.21 and 3.05 for Perl may use insecure rand() function for cryptographic functions

    Crypt::CBC versions between 1.21 and 3.05 for Perl may use the rand() function as the default source of entropy, which is not cryptographically secure, for cryptographic functions. This issue affects operating systems where "/dev/urandom'" is unavailable.  In…

  • Medium 6.5

    Net::Xero 0.044 and earlier for Perl uses insecure rand() function for cryptographic functions

    Net::Xero 0.044 and earlier for Perl uses the rand() function as the default source of entropy, which is not cryptographically secure, for cryptographic functions. Specifically Net::Xero uses the Data::Random library which specifically states that it is "Usef…

  • Medium 5.5

    WebService::Xero 0.11 for Perl uses insecure rand() function for cryptographic functions

    WebService::Xero 0.11 and earlier for Perl uses the rand() function as the default source of entropy, which is not cryptographically secure, for cryptographic functions. Specifically WebService::Xero uses the Data::Random library which specifically states tha…

  • Medium 5.5

    Net::Dropbox::API 1.9 and earlier for Perl uses insecure rand() function for cryptographic functions

    Net::Dropbox::API 1.9 and earlier for Perl uses the rand() function as the default source of entropy, which is not cryptographically secure, for cryptographic functions. Specifically Net::Dropbox::API uses the Data::Random library which specifically states th…

  • Medium 5.5

    Web::API 2.8 and earlier for Perl uses insecure rand() function for cryptographic functions

    Web::API 2.8 and earlier for Perl uses the rand() function as the default source of entropy, which is not cryptographically secure, for cryptographic functions. Specifically Web::API uses the Data::Random library which specifically states that it is "Useful m…

  • Medium 4.0

    DBIx::Class::EncodedColumn until 0.00032 for Perl uses insecure rand() function for salting password hashes in Crypt/Eksblowfish/Bcrypt.pm

    DBIx::Class::EncodedColumn use the rand() function, which is not cryptographically secure to salt password hashes. This vulnerability is associated with program files Crypt/Eksblowfish/Bcrypt.pm. This issue affects DBIx::Class::EncodedColumn until 0.00032.

  • Medium 4.0

    DBIx::Class::EncodedColumn until 0.00032 for Perl uses insecure rand() function for salting password hashes in Digest.pm

    DBIx::Class::EncodedColumn use the rand() function, which is not cryptographically secure to salt password hashes. This vulnerability is associated with program files lib/DBIx/Class/EncodedColumn/Digest.pm. This issue affects DBIx::Class::EncodedColumn until …

  • Medium 4.2

    DPA Countermeasures need reseeding

    The DPA countermeasures on Silicon Labs' Series 2 devices are not reseeded periodically as they should be. This may allow an attacker to eventually extract secret keys through a DPA attack.

  • Medium 6.5

    In  RsaKeyPairGenerator::getNumberOfIterations of RSAKeyPairGenerator.java, an incorrect implementation could cause wea…

  • Medium 5.3

    Insufficient Default OTP Shared Secret Length

    Under the default configuration, Devise-Two-Factor versions >= 2.2.0 & < 6.0.0 generate TOTP shared secrets that are 120 bits instead of the 128-bit minimum defined by RFC 4226. Using a shared secret shorter than the minimum to generate a multi-factor authent…

  • Medium 5.3

    An insufficient entropy vulnerability caused by the improper use of a randomness function with low entropy for web auth…

  • Medium 5.3

    ZendFramework Information Disclosure and Insufficient Entropy vulnerability

    In Zend Framework, `Zend_Captcha_Word` (v1) and `Zend\Captcha\Word` (v2) generate a "word" for a CAPTCHA challenge by selecting a sequence of random letters from a character set. Prior to this advisory, the selection was performed using PHP's `internal array_…

  • Medium 5.3

    An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, Exynos 990, Exynos 850, …

  • Medium —

    Insecure State Generation in laravel/socialite

    laravel/socialite versions prior to 2.0.9 are found to have an insecure state generation mechanism, potentially exposing the OAuth authentication process to security risks. The issue has been addressed in version 2.0.9 by ensuring that the state is generated …

  • Medium —

    FOSUserBundle Entropy is lost in the TokenGenerator

    ### Description Because of the usage of base_convert which looses precision for large inputs, the entropy of tokens generated by FOSUserBundle for the email confirmation and password resetting is lost. This makes these tokens much less random than they are ex…

  • Medium 6.2

    Chilkat before v9.5.0.98, allows attackers to obtain sensitive information via predictable PRNG in ChilkatRand::randomB…

  • Medium 6.8

    Uninitialized TRNG used for ECDSA after EM2/EM3 sleep for VSE devices

    TRNG is used before initialization by ECDSA signing driver when exiting EM2/EM3 on Virtual Secure Vault (VSE) devices. This defect may allow Signature Spoofing by Key Recreation.This issue affects Gecko SDK through v4.4.0.

  • Medium 5.9

    pubnub Insufficient Entropy vulnerability

    Versions of the package pubnub before 7.4.0; all versions of the package com.pubnub:pubnub; versions of the package pubnub before 6.19.0; all versions of the package github.com/pubnub/go; versions of the package github.com/pubnub/go/v7 before 7.2.0; versions …

  • Medium 5.9

    ​The affected TBox RTUs generate software security tokens using insufficient entropy. The random seed used to generate …

  • Medium 5.3

    crypto-js uses insecure random numbers

    The crypto-js package before 3.2.1 for Node.js generates random numbers by concatenating the string "0." with an integer, which makes the output more predictable than necessary.

  • Medium 5.9

    An insufficient entropy vulnerability caused by the improper use of randomness sources with low entropy for RSA key pai…

  • Medium 5.3

    Dell BSAFE Crypto-C Micro Edition, versions before 4.1.5, and Dell BSAFE Micro Edition Suite, versions before 4.6, cont…

  • Medium —

    Mattermost Server has low entropy for authorization data as an OAuth 2.0 Service Provider

    An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2, when serving as an OAuth 2.0 Service Provider. There is low entropy for authorization data.

  • Medium 5.2

    It was discovered that libICE before 1.0.9-8 used a weak entropy to generate keys. A local attacker could potentially u…

  • Medium 6.5

    It was discovered that libXdmcp before 1.1.2 including used weak entropy to generate session keys. On a multi-user syst…